darshil929 commented on issue #42846: URL: https://github.com/apache/airflow/issues/42846#issuecomment-4847121753
Thanks for the detailed explanation, that clears it up. The multi-team framing is the piece I was missing: the consumer-side control exists for team isolation, and triggering via an asset is intentionally gated by "can update the asset" rather than per-Dag access_control. The point that another team may not even know the Dag exists makes it obvious why a per-Dag trigger permission wouldn't fit. Happy to defer to that, I'll close the PR. Thanks both for taking the time to walk through it. -- 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]
