o-nikolas commented on code in PR #73295: URL: https://github.com/apache/airflow/pull/73295#discussion_r4064956318
########## airflow-core/src/airflow/cli/commands/dag_processor_command.py: ########## @@ -33,12 +34,32 @@ log = logging.getLogger(__name__) +def _get_team_name(bundle_names: list[str] | None) -> str | None: + """ + Return the team this Dag processor serves, or None when it serves no single team. + + A bundle belongs to at most one team, so the processor is team-scoped only when every + bundle it parses belongs to the same team. A processor parsing all bundles, bundles of + several teams, or a team-less bundle alongside a team's own is not team-scoped. Review Comment: This is a pretty loose definition then? I wonder if it maybe should go the other direction? If it's parsing for many teams it should be scoped for each? Rather than scoped for none? Since what's important is outages for any specific team's parsing. And if they're each dependent on the same processor, then I think that's still relevant information for each team it parses for. -- 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]
