-
Notifications
You must be signed in to change notification settings - Fork 17k
Load example DAGs from providers via ProvidersManager (continuation of #57320) #66161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
andreahlert
wants to merge
18
commits into
apache:main
Choose a base branch
from
andreahlert:pr-57320
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 17 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
36a9905
chore: move standard examples to provider
bhavaniravi a1d8210
fix: failing testcases to load examples form dagbundle
bhavaniravi 689f502
Resolve provider example DAGs via ProvidersManager
andreahlert 4586cc5
Tests: relax test_get_all_bundle_names assertion
andreahlert db1057e
Address review feedback on example DAG loading
andreahlert 88fe049
Tests: use SQLAlchemy 2.0 delete() in trigger_dagrun teardown
andreahlert 06f05b5
Tests: update bundle_name for example_python_operator
andreahlert 457e7cd
Tests: avoid double-loading example DAGs in parse_and_sync_to_db
andreahlert 84380f0
Trigger CI rerun
andreahlert aea523b
Update devel-common/src/tests_common/test_utils/db.py
andreahlert 4cf8023
Update airflow-core/src/airflow/dag_processing/bundles/manager.py
andreahlert 3c57649
Address review feedback on provider example DAG bundle discovery
andreahlert 0b18521
Remove include_examples parameter from DagBag and test helpers
andreahlert 4909626
Fix mypy and test assertion after DagBag include_examples removal
andreahlert 38b06a5
Merge remote-tracking branch 'upstream/main' into pr-66161
andreahlert 9ef9809
Drop include_examples from new DagBag callers and gate dag_maker for …
andreahlert f7c43d6
Gate DagBag include_examples on Airflow 3.3+ for older compat runs
andreahlert 30607c9
Trim 66161 newsfragment to user-visible facts
andreahlert File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,65 @@ | ||
| Provider example DAGs are exposed as dedicated bundles | ||
|
|
||
| Example DAGs that ship with provider distributions are now discovered via | ||
| ``ProvidersManager`` and registered as their own DAG bundles, one per | ||
| provider that ships an ``example_dags/`` folder. Bundle names follow the | ||
| shape ``apache-airflow-providers-<distribution>-example-dags`` (for | ||
| canonical Apache providers) or ``<distribution-name>-example-dags`` (for | ||
| third-party providers). The ``[core] load_examples`` configuration option | ||
| remains the single switch that controls whether any example bundles are | ||
| registered. | ||
|
|
||
| **What changed:** | ||
|
|
||
| - Example DAGs that previously came in under the implicit ``dags-folder`` | ||
| bundle are now persisted in ``DagBundleModel`` rows and emitted in REST | ||
| API responses (``GET /api/v2/dags/{dag_id}/dag-versions`` and the | ||
| ``bundle_name`` field on task-instance responses) under the new | ||
| per-provider bundle names. | ||
| - Nested providers such as ``apache-airflow-providers-common-sql`` are | ||
| discovered correctly (previously they were missed because discovery | ||
| walked ``airflow.providers.__path__`` directly). | ||
|
|
||
| **Behaviour changes:** | ||
|
|
||
| - Clients filtering or tracking bundles by ``"dags-folder"`` for | ||
| previously-shipped example DAGs (e.g. ``example_python_operator``) need | ||
| to update to the new per-provider bundle names. The DAG identifiers | ||
| themselves are unchanged. | ||
|
|
||
| **Removals:** | ||
|
|
||
| - The ``include_examples`` parameter has been removed from | ||
| ``DagBag.__init__``, ``DagBag.collect_dags``, ``BundleDagBag.__init__``, | ||
| and ``tests_common.test_utils.db.parse_and_sync_to_db``. Example DAG | ||
| loading is now controlled exclusively by the ``[core] load_examples`` | ||
| configuration option, which gates whether the per-provider example | ||
| bundles are registered. Callers that previously passed | ||
| ``include_examples=True`` should set | ||
| ``conf_vars({("core", "load_examples"): "true"})`` (or equivalent | ||
| configuration). Callers that previously passed | ||
| ``include_examples=False`` can drop the argument: it matches the new | ||
| default behaviour where ``DagBag`` only walks the configured | ||
| ``dag_folder`` and example DAGs come in via dedicated bundles. | ||
|
|
||
| * Types of change | ||
|
|
||
| * [ ] Dag changes | ||
| * [x] Config changes | ||
| * [x] API changes | ||
| * [ ] CLI changes | ||
| * [x] Behaviour changes | ||
| * [ ] Plugin changes | ||
| * [ ] Dependency changes | ||
| * [x] Code interface changes | ||
|
|
||
| * Migration rules needed | ||
|
|
||
| * Update clients that filter REST API responses by ``bundle_name`` to | ||
| match the new per-provider bundle names for example DAGs. | ||
| * Replace ``include_examples=True`` calls to ``DagBag`` / | ||
| ``parse_and_sync_to_db`` with | ||
| ``conf_vars({("core", "load_examples"): "true"})`` (or equivalent | ||
| configuration). The argument has been removed. | ||
| * Drop ``include_examples=False`` arguments from ``DagBag`` / | ||
| ``parse_and_sync_to_db`` calls; the default behaviour is unchanged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.