Repository navigation
Multi-Team: Add teams inspect CLI command to display team resources - #72036
Merged
Merged
Conversation
SameerMesiah97
force-pushed
the
Multi-Team-Inspect-Command
branch
from
August 24, 2026 18:07
0554d64 to
6c79f82
Compare
SameerMesiah97
marked this pull request as ready for review
August 25, 2026 19:56
SameerMesiah97
requested review from
bugraoz93,
dheerajturaga,
henry3260 and
potiuk
as code owners
August 25, 2026 19:56
o-nikolas
reviewed
Aug 28, 2026
SameerMesiah97
force-pushed
the
Multi-Team-Inspect-Command
branch
from
September 1, 2026 20:00
6c79f82 to
b92238a
Compare
SameerMesiah97
force-pushed
the
Multi-Team-Inspect-Command
branch
from
September 15, 2026 19:25
b92238a to
e94c9be
Compare
Contributor
Author
|
Requesting review for this. |
Contributor
|
Could you please update the description to contain an example of output? That would be great to see the result |
Contributor
Author
Done. |
henry3260
reviewed
Sep 16, 2026
henry3260
left a comment
Contributor
There was a problem hiding this comment.
Overall looks great only few nits
added 3 commits
September 19, 2026 16:01
Adds a new command to display the resources associated with a team. The command reports DAG bundle associations, pools, connections, and variables for the requested team, providing a single view of team-owned resources. Also adds unit tests covering teams with associated resources, empty teams, and nonexistent teams.
…ntly across table, JSON, YAML, and plain output modes, add filtering coverage for resources belonging to other teams, and update empty-team output tests.
…spect command. Add unit test for multi-team disabled scenario.
SameerMesiah97
force-pushed
the
Multi-Team-Inspect-Command
branch
from
September 19, 2026 15:14
e94c9be to
677946f
Compare
1 task done
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
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.
Description
This change introduces a new
airflow teams inspectCLI command for displaying the resources associated with a team.The command provides a consolidated view of a team's DAG bundle associations, pools, connections, and variables, making it easier to understand which resources belong to a team and to troubleshoot or prepare administrative operations.
Rationale
As multi-team deployments grow, it becomes useful to inspect a team's resources from a single command rather than querying each resource type independently.
The
teams inspectcommand provides administrators with a convenient overview of team-owned resources, complementing existing management commands such asteams verifyandteams delete.Tests
Added unit tests verifying that:
Documentation
Added CLI help text describing the new
teams inspectcommand.Backwards Compatibility
This change is additive. Existing behaviour is unchanged unless the new
teams inspectcommand is explicitly invoked.Sample Output
The following output is displayed when
airflow teams inspect team_ais executed, assuming thatteam_aexists and has the associated resources shown below:Was generative AI tooling used to co-author this PR?
Generated-by: [GPT 5.5] following the guidelines