Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add further details to replacement documentation #36485

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 7 additions & 5 deletions docs/apache-airflow/templates-ref.rst
Original file line number Diff line number Diff line change
Expand Up @@ -100,9 +100,9 @@ Deprecated variables
The following variables are deprecated. They are kept for backward compatibility, but you should convert
existing code to use other variables instead.

===================================== ====================================
===================================== ==========================================================================
Deprecated Variable Description
===================================== ====================================
===================================== ==========================================================================
``{{ execution_date }}`` the execution date (logical date), same as ``logical_date``
``{{ next_execution_date }}`` the logical date of the next scheduled run (if applicable);
you may be able to use ``data_interval_end`` instead
Expand All @@ -115,9 +115,11 @@ Deprecated Variable Description
``{{ yesterday_ds_nodash }}`` the day before the execution date as ``YYYYMMDD``
``{{ tomorrow_ds }}`` the day after the execution date as ``YYYY-MM-DD``
``{{ tomorrow_ds_nodash }}`` the day after the execution date as ``YYYYMMDD``
``{{ prev_execution_date_success }}`` execution date from prior successful DAG run

===================================== ====================================
``{{ prev_execution_date_success }}`` execution date from prior successful DAG run;
you may be able to use ``prev_data_interval_start_success``instead if
the timetable/schedule you use for the DAG defines ``data_interval_start``
compatible with the legacy ``execution_date``.
===================================== ==========================================================================

Note that you can access the object's attributes and methods with simple
dot notation. Here are some examples of what is possible:
Expand Down