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.

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

Feat/migration oss ee #1933

Merged
merged 4 commits into from
Aug 31, 2023
Merged

Feat/migration oss ee #1933

merged 4 commits into from
Aug 31, 2023

Conversation

loicmathieu
Copy link
Member

This PR refactor the way we use Flyway migrations.

Starting from now, we allow migrations out-of-order to allow migration from OSS to EE.
All current migrations has been merged in a single V_1_1 migrations that will be our new starting point, this migration is 100% backward compatible (all objects are created indempotently).
For now, OSS migrations should start with V_1_ and all EE migrations should start with V_2_.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Copy link
Member

@brian-mulier-p brian-mulier-p left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@loicmathieu loicmathieu merged commit 04e5e68 into develop Aug 31, 2023
@loicmathieu loicmathieu deleted the feat/migration-oss-ee branch August 31, 2023 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants