uranusjr commented on code in PR #43902:
URL: https://github.com/apache/airflow/pull/43902#discussion_r1837521619
##########
docs/apache-airflow/templates-ref.rst:
##########
@@ -117,24 +117,14 @@ 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,
- you may be able to use
``data_interval_end`` instead; for manually
- triggered dagruns that aren't on a
schedule, ``next_execution_date`` is
- set to ``logical_date``
``{{ next_ds }}`` the next execution date as
``YYYY-MM-DD`` if exists, else ``None``
``{{ next_ds_nodash }}`` the next execution date as
``YYYYMMDD`` if exists, else ``None``
-``{{ prev_execution_date }}`` the logical date of the previous
scheduled run (if applicable)
``{{ prev_ds }}`` the previous execution date as
``YYYY-MM-DD`` if exists, else ``None``
``{{ prev_ds_nodash }}`` the previous execution date as
``YYYYMMDD`` if exists, else ``None``
``{{ yesterday_ds }}`` the day before the execution date as
``YYYY-MM-DD``
``{{ 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;
- 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``.
=====================================
==========================================================================
Review Comment:
These should all be removed too.
--
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]
