FLYWAY ENTERPRISE

1. After a successful deployment, use flyway snapshot to save the state of the database you just deployed to in a snapshot file.  Save this snapshot to a location that is accessible to your release pipeline.
   

   flyway snapshot -source=Prod -filename=deployedSnapshot.json

   
   In the example above, "Prod" is the name of a database environment that is defined in the TOML file  and provides the connection information for the database that you want to capture in a snapshot file.
   
   
   
2. • Command-line
   • Flyway Desktop

   Before doing a deployment, use flyway check -drift to compare the snapshot saved above to the target database you're about to deploy to.  If there are any changes, then your target database has drifted and it no longer matches the expected state captured above after your last deployment.

   flyway check -drift -deployedSnapshot="deployedSnapshot.json" -environment="Prod" -failOnDrift=true

   
   

   1. Navigate to the Migration scripts page
   2. Connect to your target environment, by selecting the relevant connection from the Target database dropdown, or adding a new target configuration.
   3. Select Check from the command dropdown in the right hand pane
   4. Check the drift flag under the command dropdown
   5. Expand the Advanced settings and click Add parameters
   6. Select check.deployedSnapshot from the drop down.  You can start typing to limit the results and find the parameter you need easier.
   7. Enter deploymentSnapshot.json for the parameter value.
   8. Click Add parameter.
   9. Repeat steps f-h, but this time set check.failOnDrift to true
   10. Click Back.
   11. Click Run check
   
   
   
   
3. In this example, 1 object has changed since the snapshot was taken.  Drilling down, you can see the exact changes - a new "DriftedColumn" was added to the Customers table. 
   

Learn more

• What is a snapshot?