TriggerDagRunOperator to configure the run_id of the triggered dag

[waleedsamy]

Description

Airflow 1.10 support providing a run_id to TriggerDagRunOperator using DagRunOrder object that will be returned after calling TriggerDagRunOperator#python_callable. With #6317 (Airflow 2.0), this behavior changed and one could not provide run_id anymore to the triggered dag, which is very odd to say the least.

Use case / motivation

I want to be able to provide run_id for the TriggerDagRunOperator. In my case, I use the TriggerDagRunOperator to trigger 30K dag_run daily and will be so annoying to see them having unidentifiable run_id.

After discussing with @ashb
Suggested fixes can be

• provide a templated run_id as a parameter to TriggerDagRunOperator.
• restore the old behavior of Airflow 1.10, where DagRunOrder holds the run_id and dag_run_conf of the triggered dag
• create a new sub-class of TriggerDagRunOperator to fully customize it

Are you willing to submit a PR?

Related Issues

[ashb]

/cc @BasPH