shahar1 commented on code in PR #61258:
URL: https://github.com/apache/airflow/pull/61258#discussion_r2746952648
##########
airflow-core/docs/templates-ref.rst:
##########
@@ -21,6 +21,21 @@ Templates reference
===================
Variables, macros and filters can be used in templates (see the
:ref:`concepts:jinja-templating` section)
+Asset-triggered DAGs
+--------------------
+
+Asset-triggered DAGs in Apache Airflow 3 differ from time-based DAGs in the
+template context they provide.
+
+Asset-triggered DAGs do not have a logical date, and therefore do not provide
+time-based context variables such as ``logical_date``, ``ds``, ``ds_nodash``,
+or values derived from them.
+
+For asset-triggered DAGs, information related to the triggering run can be
+accessed via ``dag_run``. For example, ``dag_run.run_id`` can be used to
+uniquely identify a DAG run triggered by an asset event.
Review Comment:
```suggestion
Asset-triggered Dags in Apache Airflow 3 differ from time-based Dags in the
template context they provide.
Asset-triggered Dags do not have a logical date, and therefore do not provide
time-based context variables such as ``logical_date``, ``ds``, ``ds_nodash``,
or values derived from them.
For asset-triggered Dags, information related to the triggering run can be
accessed via ``dag_run``. For example, ``dag_run.run_id`` can be used to
uniquely identify a Dag run triggered by an asset event.
```
Small fix before merging ("Dag" is the current official term for an Airflow
workflow) :)
--
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]
