JH-A-Kim commented on code in PR #67994: URL: https://github.com/apache/airflow/pull/67994#discussion_r3384328021
########## airflow-core/docs/core-concepts/overview.rst: ########## @@ -177,21 +180,22 @@ Helm Chart documentation. Helm chart is one of the ways how to deploy Airflow in Separate Dag processing architecture .................................... -In a more complex installation where security and isolation are important, you'll also see the -standalone *Dag processor* component that allows to separate *scheduler* from accessing *Dag files*. -This is suitable if the deployment focus is on isolation between parsed tasks. While Airflow does not yet -support full multi-tenant features, it can be used to make sure that **Dag author** provided code is never -executed in the context of the scheduler. +The *Dag processor* is a required component in all Airflow 3 deployments. In distributed +deployments it runs as a standalone process, ensuring the *scheduler* never has direct access Review Comment: I got it! I fixed the wording in commit aedb3d4126f995ce1dc7082bbf86ecd7ebf0f010 Thank you for the help! -- 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]
