nathadfield commented on code in PR #61448:
URL: https://github.com/apache/airflow/pull/61448#discussion_r2889677419
##########
airflow-core/docs/administration-and-deployment/dag-bundles.rst:
##########
@@ -139,6 +139,96 @@ are configured so that impersonated users can access
bundle files created by the
the need for shared group permissions.
+Configuring Default Bundle Version Behavior
+--------------------------------------------
+
+When using versioned DAG bundles (such as ``GitDagBundle``), Airflow provides
flexible control
+over which bundle version is used for DAG runs through a three-level
configuration hierarchy.
+
+.. note::
+
+ Bundle versioning is only supported by certain bundle types (like
``GitDagBundle``). Local bundles
+ (``LocalDagBundle``) do not support versioning and will always use the
latest code.
+
+Precedence Hierarchy
+~~~~~~~~~~~~~~~~~~~~
+
+The bundle version used for a DAG run is determined by the following
precedence (highest to lowest):
+
+1. **DAG Level**: The DAG's ``run_on_latest_version`` parameter
+2. **Global Level**: The ``[core] run_on_latest_version`` configuration setting
+3. **System Default**: Use the original bundle version (``False`` - for
reproducibility)
Review Comment:
The system default is just False, hardcoded as the fallback when neither the
DAG-level parameter nor the global config option is set. It's not
user-configurable. I've updated the docs to make this clearer by removing the
"system default" label and just listing Default: False in the precedence.
--
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]
