SameerMesiah97 opened a new pull request, #72036:
URL: https://github.com/apache/airflow/pull/72036

   **Description**
   
   This change introduces a new `airflow teams inspect` CLI 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 inspect` command provides administrators with a convenient 
overview of team-owned resources, complementing existing management commands 
such as `teams verify` and `teams delete`.
   
   **Tests**
   
   Added unit tests verifying that:
   
   * Inspecting a team with associated resources displays its DAG bundles, 
pools, connections, and variables.
   * Inspecting a team with no associated resources reports empty sections 
while displaying the default pool.
   * Inspecting a nonexistent team exits with an appropriate error.
   
   **Documentation**
   
   Added CLI help text describing the new `teams inspect` command.
   
   **Backwards Compatibility**
   
   This change is additive. Existing behaviour is unchanged unless the new 
`teams inspect` command is explicitly invoked.
   
   ###### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: [GPT 5.5] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to