-
Notifications
You must be signed in to change notification settings - Fork 16.3k
AIP-84 Add Auth for DAG Versioning #47553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
pierrejeambrun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What type of permissions do we want on dag versions ? Do we want a new entity ? Or dag related dag access / code is enough ?
I think we should add a new entity in |
6028d26 to
444ec51
Compare
444ec51 to
aaebc9d
Compare
providers/amazon/tests/unit/amazon/aws/auth_manager/test_aws_auth_manager.py
Show resolved
Hide resolved
|
restarting the failed job. We should be good to go. (even if we know it's unrelated k8s flaky failure) |
|
merging |
* add auth to dag versions endpoints * adding new DagAccessEntity for DAG Version * feat(security): add DagAccessEntity.VERSION --------- Co-authored-by: Wei Lee <weilee.rx@gmail.com>
* add auth to dag versions endpoints * adding new DagAccessEntity for DAG Version * feat(security): add DagAccessEntity.VERSION --------- Co-authored-by: Wei Lee <weilee.rx@gmail.com>
related to #42360
^ 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.rstor{issue_number}.significant.rst, in newsfragments.