Repository navigation
Implement filter_permitted_dag_ids in AWS auth manager - #37666
Merged
Merged
Conversation
boring-cyborg
Bot
added
area:providers
provider:amazon
vincbeck
requested review from
ferruzzi and
o-nikolas
and removed request for
o-nikolas
February 29, 2024 16:28
o-nikolas
reviewed
Mar 4, 2024
ferruzzi
reviewed
Mar 4, 2024
o-nikolas
approved these changes
Mar 8, 2024
ephraimbuddy
added
the
changelog:skip
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implement
filter_permitted_dag_idsin AWS auth manager. This method leveragesbatch_is_authorizedAPI from Amazon Verified Permissions to check DAG access from the user in one call instead of N calls where N is the number of DAGs.^ 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.