Skip to content

Clarify that DAG authors can also run code in DAG File Processor - #33920

Merged
potiuk merged 2 commits into
apache:mainfrom
potiuk:small-clarification-of-security-model
Aug 30, 2023
Merged

potiuk merged 2 commits into
apache:mainfrom
potiuk:small-clarification-of-security-model

Conversation

@potiuk

@potiuk potiuk commented Aug 30, 2023

Copy link
Copy Markdown
Member

Small addition to our security model - it was not entirely clear that DAG authors can also execute code in DAG File Processor and that DAG File Processor can be run in standalone mode effectively physically separating machines where scheduler is run and where the code modified by DAG authors gets parsed.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Small addition to our security model - it was not entirely clear
that DAG authors can also execute code in DAG File Processor and
that DAG File Processor can be run in standalone mode effectively
physically separating machines where scheduler is run and where
the code modified by DAG authors gets parsed.
Comment thread docs/apache-airflow/security/security_model.rst Outdated
Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
@potiuk
potiuk merged commit 1dc6ba0 into apache:main Aug 30, 2023
@potiuk
potiuk deleted the small-clarification-of-security-model branch August 30, 2023 17:54
@potiuk potiuk added this to the Airflow 2.7.1 milestone Aug 30, 2023
@ephraimbuddy ephraimbuddy added the type:doc-only Changelog: Doc Only label Sep 1, 2023
ephraimbuddy added a commit that referenced this pull request Sep 1, 2023
)

* Clarify that DAG authors can also run code in DAG File Processor

Small addition to our security model - it was not entirely clear
that DAG authors can also execute code in DAG File Processor and
that DAG File Processor can be run in standalone mode effectively
physically separating machines where scheduler is run and where
the code modified by DAG authors gets parsed.

Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
(cherry picked from commit 1dc6ba0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants