Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fresh platform should not apply migrations #445

Closed
richard-julien opened this issue Jan 25, 2020 · 0 comments
Closed

Fresh platform should not apply migrations #445

richard-julien opened this issue Jan 25, 2020 · 0 comments
Assignees
@richard-julien
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 2.1.4

Comments

@richard-julien
Copy link
Member

Problem to Solve

Today every users starting a new platform could have some error logs due to migrations that should not be applied. Its not really a problem but its confusing. We need to improve the migration proces to split the init phase and rely on the last migration date to know if we need to play migrations or not

Current Workaround

No

Proposed Solution

  • Move the 2 firsts migrations to the init phase of the platform.
  • Change migration code to support a status without migration
  • At fresh start, no migration must be played
  • With an existing platform, check the migration status date to apply only new migrations
@richard-julien richard-julien self-assigned this Jan 25, 2020
@richard-julien richard-julien added the feature use for describing a new feature to develop label Jan 25, 2020
@richard-julien richard-julien added this to the Release 2.1.4 milestone Jan 25, 2020
@richard-julien richard-julien mentioned this issue Jan 25, 2020
Merged
@richard-julien richard-julien changed the title Migration should not apply migrations on a fresh platform Fresh platform should not apply migrations Jan 25, 2020
SamuelHassine pushed a commit that referenced this issue Jan 26, 2020
@richard-julien
[api] Introduce new migration system (#445)
444ea9e
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@richard-julien richard-julien

Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 2.1.4
Development

No branches or pull requests
2 participants
@richard-julien @SamuelHassine