Skip to content

Flyway Database Migrations Doesn't Support State-Based Deployments #1630

@chrishager82

Description

@chrishager82

Step template

Flyway Database Migrations

Step version

15

Octopus version

2025.4.4847

Step template parameter inputs

No response

What happened

We're working on integrating Flyway into our CI/CD deployment processes to replace SQL Automation. We're exploring the state-based change and deploy option, but encountering some roadblocks.
We found the Octopus Step Template for Flyway Migration is outdated on the following:

  1. State-based Deployments
  2. Primarily the inclusion of the ‘Prepare’ and ‘Deploy’ commands which are needed for actual deployment and any of their required parameters
  3. Change Reports with Check Changes command
  4. Generating report based upon snapshots
  5. The default check changes always runs with the -dryrun flag which we're not sure if that overrides comparing snapshots
  6. Parameters to supply the snapshots should be added to the Step Template. The workaround is to add it to the ‘additional parameters’
  7. The reports generated are as if the build database is empty. Even if the build database has the flyway schema history and all the tables of the target database already, the report will show all tables to be ‘Added’ instead of the new migration scripts that are to be applied. This
  8. Buildurl is being deprecated. There should be a buildEnvironment added to help with the transition.

Reproduction steps

Configure the step template using existing options and parameters; Prepare and Deploy are not available in the 'Flyway Command' field.

More Information

We opened a case with Red Gate first (340726), they advised us to log an issue with the step template.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions