Move IMPORT_ERROR from DAG related permissions to view related permissions
#37292
Conversation
This file contains 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
vincbeck
requested review from
ephraimbuddy and
pierrejeambrun
as code owners
boring-cyborg
bot
added
area:API
jedcunningham
approved these changes
Feb 9, 2024
vincbeck
changed the title
IMPORT_ERROR from DAG related permissions to view related permissionsIMPORT_ERROR from DAG related permissions to view related permissions
vincbeck
force-pushed
the
vincbeck/import_errors
branch
from
749416f
to
d5b24ff
Compare
dirrao
approved these changes
Feb 10, 2024
eladkal
approved these changes
Feb 10, 2024
Taragolis
approved these changes
Feb 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Import errors should be treated like cluster activity, plugins, ... They are not part of DAG information.
^ 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.