As an engineer, I want db-init to run again, so that database migrations can occur.
Acceptance Criteria
[ ] db-init job in ArgoCD executes successfully
Not included in this work
A future ticket will be created to address db-init's place as an application versus being a job which is executed alongside relevant applications' deployments. This ticket is only intended to fix the current flyway migration issues preventing the job from executing successfully.
Notes about work
Flyway migration to version 1.7 seems to have been executed and then reverted, as a simultaneous change was made in version 2.0. This is resulting in a failed migration, with the exception reading "Detected applied migration not resolved locally: 1.7"
There is a PR up currently which sets the flag "flyway.ignoreMissingMigrations=true", which may resolve the issue.
Running a repair job with flyway may also resolve the issue if the above flag does not, which can be added before the migrate call in our startup scripts for the app.
User Story
As an engineer, I want db-init to run again, so that database migrations can occur.
Acceptance Criteria
[ ] db-init job in ArgoCD executes successfully
Not included in this work
A future ticket will be created to address db-init's place as an application versus being a job which is executed alongside relevant applications' deployments. This ticket is only intended to fix the current flyway migration issues preventing the job from executing successfully.
Notes about work