WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@o-nikolas
Copy link
Contributor

If someone has configured a team, but has not added any executors to it, allow the team to then use the default global executor (which we enforce must exist). This was always possible but previously had to be configured directly in the tasks/dags, now it will be used by default.


^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

If someone has configured a team, but has not added any executors to it,
allow the team to then use the default global executor (which we enforce
must exist). This was always possible but previously had to be
configured directly in the tasks/dags, now it will be used by default.
@potiuk potiuk merged commit 7e97872 into apache:main Dec 7, 2025
65 checks passed
amoghrajesh pushed a commit to astronomer/airflow that referenced this pull request Dec 8, 2025
If someone has configured a team, but has not added any executors to it,
allow the team to then use the default global executor (which we enforce
must exist). This was always possible but previously had to be
configured directly in the tasks/dags, now it will be used by default.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants