potiuk commented on code in PR #36513: URL: https://github.com/apache/airflow/pull/36513#discussion_r1438896755
########## 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: Thought a bit and I think I will simply add much simpler diagram very much like the original one - showing "self-contained" installation - without workers and triggerers and with single user and make it the first diagram - with explanation that this is the simplest configuration and explaination that it only serves very basic installation. This way the diagrams will get gradually more complex and showing "true" nature of some of the decisions made, while not confusing the users who **just** want to start their journey with Airflow. I believe that will satisfy both - your desire @BasPH to have things simple and my desire to use the architecture diagrams of ours to explain some design decisions we have and to explain those who are looking for self-deployment of Airflow and want to understand our intentions. WDYT? -- 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