Move DAG bundle config into config, not db #44924
Merged
Conversation
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
jedcunningham
requested review from
ephraimbuddy,
potiuk,
XD-DENG and
ashb
as code owners
boring-cyborg
bot
added
area:db-migrations
jedcunningham
force-pushed
the
bundles_from_config
branch
from
9e253a0 to
d28caa7
Compare
jedcunningham
commented
Dec 14, 2024
dstandish
reviewed
Dec 16, 2024
dstandish
reviewed
Dec 16, 2024
dstandish
reviewed
Dec 16, 2024
dstandish
approved these changes
Dec 16, 2024
This moves the DAG bundle config into the Airflow config, instead of being in the db. This: - makes it much easier to configure a fresh Airflow instance - no api/cli calls required - avoids some security concerns by ensuring only deployment managers, with direct access to the instance, can configure these The primary downside is this does mean you cannot reconfigure an existing bundle in a running Airflow instance.
jedcunningham
force-pushed
the
bundles_from_config
branch
from
a1905fe to
58dc4d1
Compare
dstandish
reviewed
Dec 17, 2024
dstandish
reviewed
Dec 17, 2024
dstandish
approved these changes
Dec 17, 2024
|
Remaining failure is unrelated. |
This was referenced Dec 19, 2024
LefterisXefteris
pushed a commit
to LefterisXefteris/airflow
that referenced
this pull request
Jan 5, 2025
This moves the DAG bundle config into the Airflow config, instead of being in the db. This: - makes it much easier to configure a fresh Airflow instance - no api/cli calls required - avoids some security concerns by ensuring only deployment managers, with direct access to the instance, can configure these The primary downside is this does mean you cannot reconfigure an existing bundle in a running Airflow instance.
got686-yandex
pushed a commit
to got686-yandex/airflow
that referenced
this pull request
Jan 30, 2025
This moves the DAG bundle config into the Airflow config, instead of being in the db. This: - makes it much easier to configure a fresh Airflow instance - no api/cli calls required - avoids some security concerns by ensuring only deployment managers, with direct access to the instance, can configure these The primary downside is this does mean you cannot reconfigure an existing bundle in a running Airflow instance.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This moves the DAG bundle config into the Airflow config, instead of being in the db. This:
The primary downside is this does mean you cannot reconfigure an existing bundle in a running Airflow instance.