Make DB unsafe so we can run migrations #1
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.
Upgrade process:
This should be run twice, once with a cloned DB as a dry run, and then again with the live DB.
In order to do a zero downtime migration, we need a copy of hydra running that will continue to work after we apply migrations.
This fix should allow for that, just need to build our own docker container.
Then, if we run migrations, we should end up with these changes:
which should continue to work since no columns are being dropped