Support multiple Git DAG bundles - #6
Merged
Merged
Conversation
eugene-panin
force-pushed
the
agent/multi-git-dag-bundles
branch
from
July 22, 2026 17:42
a240c68 to
e529416
Compare
eugene-panin
changed the title
eugene-panin
marked this pull request as ready for review
July 22, 2026 17:49
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
--bundle-manifestto load multiple Git-backed DAG sources into one Airflow instance.GitDagBundlefor every source.Rationale
The workbench remains shared infrastructure for trusted products. DAG entrypoints may come from separate repositories while product business logic stays with each product. Python dependencies are never installed while parsing a DAG: a multi-source deployment uses an explicit, tested shared image with pinned product package revisions.
Validation
python3 -m py_compile bin/etl-workbenchpython3 -m unittest discover -s tests -v— 3 tests passedBoundary
This separates operational ownership through product-specific Connections, Pools, and object prefixes. It does not make the local workbench an isolation boundary for untrusted DAG code.