Verify team existence on Execution loading#55806
Merged
o-nikolas merged 1 commit intoSep 22, 2025
Merged
Conversation
Contributor
Author
vincbeck
reviewed
Sep 18, 2025
vincbeck
reviewed
Sep 18, 2025
vincbeck
approved these changes
Sep 18, 2025
ramitkataria
approved these changes
Sep 18, 2025
ramitkataria
left a comment
Contributor
There was a problem hiding this comment.
A minor suggestion but otherwise looks good!
If bad configuration was provided (user tried to configure an executor for a team that does not exist) then throw an exception and do not allow execution loading to complete (and Airflow Scheduler to start).
446e574 to
8219b79
Compare
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
3 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.
If bad configuration was provided (user tried to configure an executor for a team that does not exist) then throw an exception and do not allow execution loading to complete (and Airflow Scheduler to start).
^ 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 airflow-core/newsfragments.