Align TriggerDagRunOperator with logical date terminology

[eladkal]

Spawn of #19264

By the way, since execution_date has been renamed to logical_date, but TriggerDagRunOperator still uses this nomenclature, shouldn't this be changed? Like so:

• rename the execution_date parameter to logical_date
• using the execution_date parameter in this class would call logical_date for backward compatibility, after raising a deprecation warning

If this makes sense, I can create a new issue about it.

Originally posted by @augusto-herrmann in #19264 (comment)

[frankcash]

@eladkal I wonder if execution_date is still "valid" due to the fact that the API call https://github.com/apache/airflow/blob/main/airflow/operators/trigger_dagrun.py#L136-L142 takes execution_date as a parameter. https://github.com/apache/airflow/blob/main/airflow/api/common/trigger_dag.py#L31-L38

[eladkal]

We may need to allign other parts of the code

[github-actions]

This issue has been automatically marked as stale because it has been open for 365 days without any activity. There has been several Airflow releases since last activity on this issue. Kindly asking to recheck the report against latest Airflow version and let us know if the issue is reproducible. The issue will be closed in next 30 days if no further activity occurs from the issue author.

[augusto-herrmann]

I have just checked the documentation for Airflow 2.7.2 and the TriggerDagRunOperator still has a parameter named execution_date and does not have a parameter named logical_date.

So the issue still persists in current Airflow.

PR #26925 was supposed to fix this, but got closed by the author without merging.