This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a commit to branch v2-7-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 9262b4dacc2b2b268d9b745833f06823a9660c07
Author: jayljohnson <jljohn00+git...@gmail.com>
AuthorDate: Fri Oct 13 21:31:51 2023 -0700
Update dags.rst to put SubDag deprecation note right after the SubDag
section heading (#34925)
To save time for people by letting them know up front that SubDag feature
is deprecated and TaskGroup's should be used instead.
(cherry picked from commit 8f93f68e3536ddec212cbac4857e2f094f446d85)
---
docs/apache-airflow/core-concepts/dags.rst | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/docs/apache-airflow/core-concepts/dags.rst
b/docs/apache-airflow/core-concepts/dags.rst
index aa95699ab8..5069eca9f8 100644
--- a/docs/apache-airflow/core-concepts/dags.rst
+++ b/docs/apache-airflow/core-concepts/dags.rst
@@ -677,6 +677,11 @@ This is especially useful if your tasks are built
dynamically from configuration
SubDAGs
-------
+.. note::
+
+ SubDAG is deprecated hence TaskGroup is always the preferred choice.
+
+
Sometimes, you will find that you are regularly adding exactly the same set of
tasks to every DAG, or you want to group a lot of tasks into a single, logical
unit. This is what SubDAGs are for.
For example, here's a DAG that has a lot of parallel tasks in two sections:
@@ -754,10 +759,6 @@ You can see the core differences between these two
constructs.
| Simple construct declaration with context manager | Complex DAG
factory with naming restrictions |
+--------------------------------------------------------+--------------------------------------------------------+
-.. note::
-
- SubDAG is deprecated hence TaskGroup is always the preferred choice.
-
Packaging DAGs
