allow migration jobs and init containers to be optional #22195
Conversation
github-actions
bot
added
the
okay to merge
|
The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
|
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
github-actions
bot
added
the
full tests needed
@jedcunningham yeah I wasn't sure if a single flag would be better and went with more flexibility. |
|
Awesome work, congrats on your first merged pull request! |
|
Thanks @ajbosco! Congrats on your first commit, at least in the last few years (bot got confused 🤷♂️) 🎉 |
Currently, the Helm Chart forces using the migration job to run db migrations, but this has a few issues (not supporting
--waitand--atomichelm installs being the biggest. This PR makes that job (and the accompanying init containers on deployments) optional. All defaults match the existing behavior so nothing should change for current Chart users.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.