vincbeck commented on issue #42846: URL: https://github.com/apache/airflow/issues/42846#issuecomment-4846881401
> Where I was coming from is more the producer side. Normally, to emit one of these events you'd have to run a producing Dag, which means you need permission on that Dag. The API lets anyone with the global "create on Assets" permission emit the event directly and skip that, and that's the part that felt off to me. To me that's intended, both should be decoupled. By giving permissions to someone to update an asset, you indirectly allow this same persona to trigger indirectly any Dag that are scheduled bas on that asset. At least that's my understanding, very happy to hear others opinion :) -- 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]
