chore(jobsdb): add support for schema migration changesets to run always #2746
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.
Description
When running separate
gw
andprocessor
instances we cannot control the order that they get upgraded or how schema migrations get executed. Additionally, we cannot guarantee that while agw
schema migration is running or after it completes, aprocessor
running an older release will not create new tables using a previous schema.Changesets that run always can help in such scenarios, by bringing non-migrated tables into a usable state during a version upgrade or after starting up following a panic caused by an incompatible jobsdb table schema encounter.
Additional items
down
sql migration changesets since we are never performing a down migration, so these scripts are not used and have never been tested.Notion Ticket
Link
Security