Skip to content

Allow a Job to be associated with several teams - #73561

Merged
vincbeck merged 1 commit into
apache:mainfrom
aws-mwaa:vincbeck/job-multi-team
Sep 24, 2026
Merged

vincbeck merged 1 commit into
apache:mainfrom
aws-mwaa:vincbeck/job-multi-team

Conversation

@vincbeck

Copy link
Copy Markdown
Contributor

A Job's team scope was a single nullable column, which cannot describe a Dag processor that parses bundles belonging to more than one team.

There is no breaking change here, adding team as part of the job API response has not been released yet. Also, this is related to multi-team, which is still experimental.

Raised in review of #73295.


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • 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, 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.

@o-nikolas o-nikolas left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

A couple nits but looks good to me otherwise. Needs rebasing as well.

Comment thread airflow-core/src/airflow/api/common/airflow_health.py Outdated
Comment thread airflow-core/src/airflow/jobs/triggerer_job_runner.py
@vincbeck
vincbeck force-pushed the vincbeck/job-multi-team branch from 7583ca4 to 3a9b057 Compare September 23, 2026 19:42
A Job's team scope was a single nullable column, which cannot describe a
Dag processor that parses bundles belonging to more than one team. Scoping
such a processor to no team at all loses the information that its work is
relevant to each of those teams, so team coverage in the health endpoint
and the team column in the UI cannot be derived from it.

Raised in review of apache#73295.
@vincbeck
vincbeck force-pushed the vincbeck/job-multi-team branch from 3a9b057 to 3ef5229 Compare September 24, 2026 13:50
@vincbeck
vincbeck merged commit 02dff07 into apache:main Sep 24, 2026
303 of 304 checks passed
@vincbeck
vincbeck deleted the vincbeck/job-multi-team branch September 24, 2026 15:53
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.

2 participants