hasansyed107 commented on issue #72706: URL: https://github.com/apache/airflow/issues/72706#issuecomment-5616260682
Hi! I took a look at the current implementation, and it seems the team-scoped resource change spans several layers. For Pool and Variable, the existing models already carry `team_name`, but their database uniqueness/lookups are still globally scoped. These seem like a relatively self-contained first step. The Connection and especially DAG cases appear to have a larger impact because `dag_id` is currently part of the core identity/foreign-key model. Would it make sense to start by implementing team-scoped uniqueness and lookup semantics for Pool and Variable as a first PR, and handle the larger DAG/connection changes separately? If that scope makes sense, I'd be happy to work on the first part. -- 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]
