Dheeraj Turaga

> > > If we already have it in the audit log could we extract it from there in the ui/api instead of adding it to dag run table?na >...

@bbovenzi , @ashb what about the use case where we want the task to `if triggering_user == someone; do something` . Being able to look at the event log on...

@ashb, our use case basically has many users triggering a single dag with different parameters. Its hard to identify which dag run was triggered by whom when you have a...

@ashb, @bbovenzi the `trigger_dag_run` event isn't even associated with a run_id and makes it even harder to identify which runs are triggered by me when many users trigger the same...

@bbovenzi I would like to see a better Event/Action log aswell. However, I still think having `triggering_user` in the dag_run model is useful. It opens up a possibility of having...

Just for reference, in Airflow 3, retrieving the triggering user from event logs requires the following approach. I've encapsulated the access_token handling within the `get_airflow_client_configuration` method for clarity. That said,...