[v3-0-test] Initialize custom variables before running db-reset (#54324) #54327
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
Before that change, when you set custom variables or intialization in airflow-breeze-config, the initialization was kind of wrongly done. a) in case of regular breeze command, it was done AFTER db-reset b) when start-airflow was done, the initialization was done during the start-airflow - separately - which was kinda strangely duplicated This change unifies it - the initialization of custom variables and scripts happens before we run db-reset or check if we should start airflow. (cherry picked from commit 9334484) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
gopidesupavan
requested review from
ashb,
gopidesupavan and
potiuk
as code owners
gopidesupavan
removed
the
backport-to-v3-1-test
54 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Before that change, when you set custom variables or intialization in
airflow-breeze-config, the initialization was kind of wrongly done.
a) in case of regular breeze command, it was done AFTER db-reset
b) when start-airflow was done, the initialization was done during
the start-airflow - separately - which was kinda strangely duplicated
This change unifies it - the initialization of custom variables and
scripts happens before we run db-reset or check if we should start
airflow.
(cherry picked from commit 9334484)
Co-authored-by: Jarek Potiuk jarek@potiuk.com