You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by ep...@apache.org on 2022/08/15 18:44:43 UTC

[airflow] 07/45: Note how DAG policy works with default_args (#24804)

This is an automated email from the ASF dual-hosted git repository.

ephraimanierobi pushed a commit to branch v2-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit 98baf6054b0ffb9277508be871363a9362ac4c76
Author: Mario Taddeucci <ma...@gmx.com>
AuthorDate: Wed Aug 3 04:31:25 2022 -0300

    Note how DAG policy works with default_args (#24804)
    
    Co-authored-by: Tzu-ping Chung <ur...@gmail.com>
    (cherry picked from commit 298be502c35006b7c3f011b676dbb4db0633bc74)
---
 docs/apache-airflow/concepts/cluster-policies.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/apache-airflow/concepts/cluster-policies.rst b/docs/apache-airflow/concepts/cluster-policies.rst
index e1c664660a..8bec4db4c3 100644
--- a/docs/apache-airflow/concepts/cluster-policies.rst
+++ b/docs/apache-airflow/concepts/cluster-policies.rst
@@ -54,6 +54,10 @@ This policy checks if each DAG has at least one tag defined:
 
     To avoid import cycles, if you use ``DAG`` in type annotations in your cluster policy, be sure to import from ``airflow.models`` and not from ``airflow``.
 
+.. note::
+
+    DAG policies are applied after the DAG has been completely loaded, so overriding the ``default_args`` parameter has no effect. If you want to override the default operator settings, use task policies instead.
+
 Task policies
 -------------