potiuk commented on code in PR #36513: URL: https://github.com/apache/airflow/pull/36513#discussion_r1438892198
########## docs/apache-airflow/core-concepts/overview.rst: ########## @@ -43,13 +43,26 @@ An Airflow installation generally consists of the following components: Basic airflow architecture -------------------------- -This is the basic architecture of Airflow that you'll see in simple installations: +This is the basic architecture of Airflow that you'll see in simple installations. + +Note that even in the simple installation, Airflow Webserver does not access the DAG files directly +(the code you see in the Code tab of the UI is synchronized via the metadata database). + +This is to allow for a more secure deployment, where the webserver has never the need or even +possibility to executed code submitted by DAG authors, the only custom code that webserver can +execute are the plugins and those should be only installed and deployed by the Airflow Deployment Manager. Review Comment: This is a source of major confusion. Many our users still think that webserver accesses the DAG files and needs it even 3 years after releasing Airflow 2. I've been answering at least 10 times to our users that this is not the case as they still continued to deploy Airflow webserver WITH DAG folder even if this was useless. I believe we failed to communicate that - that's why I added it here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
