![]() ![]() ![]() Image: docker://flyway/flyway:latest-alpineįLYWAY_LOCATIONS: $ I also by luck happened to notice that all my actions steps were running at the same time – but thanks to this blog post from Bryan Hogan I was able to find the neat little “uses” command, so that fixed that issue….ĭescription: Migrate database in Github Action using latest Flyway Docker Containerĭescription: The jdbc url to use to connect to the databaseĭescription: The user to use to connect to the databaseĭescription: The password to use to connect to the databaseĭescription: Comma-separated list of locations to scan recursively for migrationsĭescription: Which of the Flyway commands you would like Flyway to runĭescription: Would you like clean disabled (true or false)ĭescription: Would you like to baseline on migrate (true or false)ĭescription: What is your baseline version If i add -baselineOnMigrate=true to the action, then it will baseline my Build database too, meaning it won’t run the baseline and my build will fail so I will need to pass an additional argument to my YAML somehow… * sigh* back to the Action. The solution to #1 is SUPER easy fortunately but the solution to #2 has me thinking. Otherwise Flyway will, like I experienced, fail the deployment because there are existing objects in the PROD database… obviously. ![]() Flyway Desktop generates the baseline, mine being V001_20211130101136_baseline.sql so I need it to baseline ( but not run) V001_20211130101136 when Flyway goes to deploy. I forgot to include the Baseline on Migrate and Baseline Migration Version arguments like I did with GitLab. ![]() “.\SQL doesn’t exist”), which is obvious, because I’m a numpty and forgot to change this to instead point at my “migrations” location instead.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |