JH-A-Kim commented on code in PR #67994: URL: https://github.com/apache/airflow/pull/67994#discussion_r3384250971
########## airflow-core/docs/core-concepts/overview.rst: ########## @@ -159,16 +162,16 @@ and where various roles of users are introduced - *Deployment Manager*, **Dag au **Operations User**. You can read more about those various roles in the :doc:`/security/security_model`. In the case of a distributed deployment, it is important to consider the security aspects of the components. -The *webserver* does not have access to the *Dag files* directly. The code in the ``Code`` tab of the -UI is read from the *metadata database*. The *webserver* cannot execute any code submitted by the +The *API server* does not have access to the *Dag bundles* directly. The code in the ``Code`` tab of the +UI is read from the *metadata database*. The *API server* cannot execute any code submitted by the **Dag author**. It can only execute code that is installed as an *installed package* or *plugin* by the **Deployment Manager**. The **Operations User** only has access to the UI and can only trigger Dags and tasks, but cannot author Dags. -The *Dag files* need to be synchronized between all the components that use them - *scheduler*, -*triggerer* and *workers*. The *Dag files* can be synchronized by various mechanisms - typical -ways how Dags can be synchronized are described in :doc:`helm-chart:manage-dag-files` of our -Helm Chart documentation. Helm chart is one of the ways how to deploy Airflow in K8S cluster. +The *Dag processor*, *triggerer* and *workers* all need access to the *Dag bundles*. The *scheduler* reads the serialized Dag from the *metadata database* and does not need direct access to the *Dag bundles*. Review Comment: Ah you are right, thats my bad. Fixed now in commit 0823e78e50c90f72bd993e0ab531724e8e317f46 "Triggerer Limitation: DAG bundles are not initialized in the triggerer component. " from [Dag Bundles](https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/dag-bundles.html) thank you! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
