fix: allow out-of-order Flyway migrations for V110 #569
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/flyway-out-of-order"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
API container restart loop. Flyway validates that V110 not applied but V111 is.
Outcome:
Validate failed: Migrations have failed validationRoot cause: V111 merged directly to main before V110 (separate branch).
V110 now can't apply because Flyway detects higher version (V111) already applied.
Fix
Add
spring.flyway.out-of-order=trueso Flyway applies V110 despite V111already being present. V110 adds
domain_keycolumns to retrospective runs tables.Verification
flyway_schema_historyshows V110 applied after V111