Propagate triggering user to child DAG runs via TriggerDagRunOperator#65747
Merged
dheerajturaga merged 1 commit intoMay 4, 2026
Merged
Conversation
Contributor
|
CI needs fixing. |
Collaborator
|
What if there isn't a user? Would it make sense to fall back to the DAG ID (or something like that)? |
Previously, when a task used TriggerDagRunOperator to trigger a child DAG,
the child run's triggering_user_name was left unset and the UI displayed
it as anonymous. The information was already captured on the parent
DagRun but never forwarded through the Execution API.
The POST /execution/dag-runs/{dag_id}/{run_id} endpoint now looks up the
calling task instance's parent DagRun and forwards its triggering_user_name
to the new child run. Chains of TriggerDagRunOperator runs now show the
original human user end-to-end
dheerajturaga
force-pushed
the
bugfix/propagate-username-child-dagrun
branch
from
9e9114b to
8b717b1
Compare
Member
Author
if there isn't a user, it would default to None just like before. falling back to dagid for triggering user would be incorrect |
Member
Author
CI was broken on main, it just got fixed in #65748 |
dheerajturaga
added
backport-to-v3-2-test
shubhamraj-git
approved these changes
May 2, 2026
Contributor
shubhamraj-git
left a comment
shubhamraj-git
left a comment
There was a problem hiding this comment.
Thanks for the patch. Looks fine.
Tested locally, works as expected.
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
May 4, 2026
…gRunOperator (apache#65747) Previously, when a task used TriggerDagRunOperator to trigger a child DAG, the child run's triggering_user_name was left unset and the UI displayed it as anonymous. The information was already captured on the parent DagRun but never forwarded through the Execution API. The POST /execution/dag-runs/{dag_id}/{run_id} endpoint now looks up the calling task instance's parent DagRun and forwards its triggering_user_name to the new child run. Chains of TriggerDagRunOperator runs now show the original human user end-to-end (cherry picked from commit f06df11) Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
May 4, 2026
…gRunOperator (apache#65747) Previously, when a task used TriggerDagRunOperator to trigger a child DAG, the child run's triggering_user_name was left unset and the UI displayed it as anonymous. The information was already captured on the parent DagRun but never forwarded through the Execution API. The POST /execution/dag-runs/{dag_id}/{run_id} endpoint now looks up the calling task instance's parent DagRun and forwards its triggering_user_name to the new child run. Chains of TriggerDagRunOperator runs now show the original human user end-to-end (cherry picked from commit f06df11) Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
potiuk
pushed a commit
that referenced
this pull request
May 10, 2026
…gRunOperator (#65747) Previously, when a task used TriggerDagRunOperator to trigger a child DAG, the child run's triggering_user_name was left unset and the UI displayed it as anonymous. The information was already captured on the parent DagRun but never forwarded through the Execution API. The POST /execution/dag-runs/{dag_id}/{run_id} endpoint now looks up the calling task instance's parent DagRun and forwards its triggering_user_name to the new child run. Chains of TriggerDagRunOperator runs now show the original human user end-to-end (cherry picked from commit f06df11) Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
potiuk
pushed a commit
that referenced
this pull request
May 10, 2026
…gRunOperator (#65747) Previously, when a task used TriggerDagRunOperator to trigger a child DAG, the child run's triggering_user_name was left unset and the UI displayed it as anonymous. The information was already captured on the parent DagRun but never forwarded through the Execution API. The POST /execution/dag-runs/{dag_id}/{run_id} endpoint now looks up the calling task instance's parent DagRun and forwards its triggering_user_name to the new child run. Chains of TriggerDagRunOperator runs now show the original human user end-to-end (cherry picked from commit f06df11) Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, when a task used TriggerDagRunOperator to trigger a child DAG,
the child run's triggering_user_name was left unset and the UI displayed
it as anonymous. The information was already captured on the parent
DagRun but never forwarded through the Execution API.
The POST /execution/dag-runs/{dag_id}/{run_id} endpoint now looks up the
calling task instance's parent DagRun and forwards its triggering_user_name
to the new child run. Chains of TriggerDagRunOperator runs now show the
original human user end-to-end
Was generative AI tooling used to co-author this PR?
ClaudeCode