potiuk commented on issue #42846: URL: https://github.com/apache/airflow/issues/42846#issuecomment-4846986309
I 100% agree with Vincent. This is as designed. And also the way how Multi-team is designed around that. By default anyone can create any asset and that's fine. And when you create Dag to be triggered by it, be default it is for the whole team. There we introduced "consumer" side control - but only because "Teams" should be isolated, we still allow anyone who can update asset to trigger the Dag in the same team by default. And Dag Author can add optionally "other teams can trigger the Dag" - but also that is not based on "can you trigger Dag" - because practically speaking the other Team does not even **KNOW** that particular Dag exists - so there is even **NO WAY** to give the other team permissions to allow them trigger the Dags from the other team. -- 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]
