molcay commented on PR #39165: URL: https://github.com/apache/airflow/pull/39165#issuecomment-2145604905
Hi @jscheffl, Thank you for your message. The thing is that at the beginning we were trying to address a very specific use case to distinguish operator-triggered runs and scheduled runs. While trying to find a solution, I implemented #37087 but we had a discussion on that PR and as a conclusion we decided to add the `triggered_by` field to distinguish the source for the dag run. It might be handy to know which component triggered the DAG Run. Since we can trigger a DAG run with different sources, it was making sense to store this information in the table. To be able to distinguish who started the run from the UI, or which operator/task triggered the run in the code a bit more excessive, at least at this point. Maybe adding a record to LOG/audit log table can be useful to know which specific task triggered the run or who started the run from the UI. -- 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]
