Scope plugin listeners to teams in multi-team airflow#69989
Draft
o-nikolas wants to merge 1 commit into
Draft
Conversation
When multi-team mode is enabled, a team-scoped plugin's listeners now only receive events for that team's Dags, while global plugins (no team_name) continue to receive everything. Component-lifecycle, asset, and import-error hooks remain global because they are not associated with a single team. On the worker the team is taken from the server-provided task instance context rather than local configuration, so scoping does not depend on whether core.multi_team happens to be set on the worker which is not entirely reliable.
boring-cyborg
Bot
added
area:API
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
1 participant
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.
When multi-team mode is enabled, a team-scoped plugin's listeners now only receive events for that team's Dags, while global plugins (no team_name) continue to receive everything. Component-lifecycle, asset, and import-error hooks remain global because they are not associated with a single team.
On the worker the team is taken from the server-provided task instance context rather than local configuration, so scoping does not depend on whether core.multi_team happens to be set on the worker which is not entirely reliable.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.