Skip to content

Conversation

@o-nikolas
Copy link
Contributor

@o-nikolas o-nikolas commented Jan 13, 2026

Add validation to ensure global executors are specified before any team executors, since we do not want them to be the default global executor.

Was generative AI tooling used to co-author this PR?

  • Yes (please specify the tool below)

Cline


  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

Add validation to ensure global executors are specified before any
team executors, since we do not want them to be the default global
executor.
@boring-cyborg boring-cyborg bot added the area:Executors-core LocalExecutor & SequentialExecutor label Jan 13, 2026
@eladkal eladkal added this to the Airflow 3.2.0 milestone Jan 13, 2026
Comment on lines +255 to +259
if team_name is not None:
seen_team_executor = True
elif seen_team_executor:
# Found a global executor after we've already seen a team executor
raise AirflowConfigException(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why setting a boolean and then raising an exception if that flag is True (but in a different loop iteration)? So if there is one executor configured and this executor is team based, it will not raise an exception?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:Executors-core LocalExecutor & SequentialExecutor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants