ferruzzi commented on code in PR #53831:
URL: https://github.com/apache/airflow/pull/53831#discussion_r2283439893
##########
airflow-core/docs/administration-and-deployment/logging-monitoring/callbacks.rst:
##########
@@ -95,22 +101,43 @@ Before each task begins to execute, the
``task_execute_callback`` function will
with DAG(
dag_id="example_callback",
- schedule=None,
- start_date=pendulum.datetime(2021, 1, 1, tz="UTC"),
- dagrun_timeout=datetime.timedelta(minutes=60),
- catchup=False,
on_success_callback=dag_success_alert,
default_args={"on_execute_callback": task_execute_callback},
- tags=["example"],
):
task1 = EmptyOperator(task_id="task1",
on_failure_callback=[task_failure_alert])
task2 = EmptyOperator(task_id="task2")
task3 = EmptyOperator(task_id="task3")
task1 >> task2 >> task3
-.. note::
- As of Airflow 2.6.0, callbacks now supports a list of callback functions,
allowing users to specify multiple functions
- to be executed in the desired event. Simply pass a list of callback
functions to the callback args when defining your DAG/task
- callbacks: e.g ``on_failure_callback=[callback_func_1, callback_func_2]``
-
Full list of variables available in ``context`` in :doc:`docs
<../../templates-ref>` and `code
<https://github.com/apache/airflow/blob/main/task-sdk/src/airflow/sdk/definitions/context.py>`_.
+
+
+Using Notifiers
+^^^^^^^^^^^^^^^
+
+You can use Notifiers in your ``DAG`` definition by passing it as an argument
to the ``on_*_callbacks``.
Review Comment:
Fair, I'll make the change throughout that file.
--
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]
