Add regular ecto migration with numeric ids v2 schemas #2768
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.
Changes
This work is on top of, and against #2762.
Normally, for live environments the migration will be done via
DataMigration.NumericIDs
module (TBD). In which casePASS_V2_SCHEMA_MIGRATION
environment variable needs to be set, to only make the standard migrate
command write an entry into
schema_migrations
table.For tests, and entirely new self-hosted instances however,
we want to keep the ability of preparing the database without enforcing
any data migration.
Tests
Changelog
Documentation
Dark mode