Deploying database changes using Flyway
Published 11 October 2021
- Deployment approaches with Flyway
- Deploying database changes manually
- Automating deployment using a CI/CD tool
- Common state-based deployment scripts
- Common migrations-based deployment scripts
- Example state-based CI/CD Pipelines
- Example migrations-based CI/CD Pipelines
- Tutorial - Installing Flyway on your CI/CD agents by downloading and unzipping
- Tutorial - Generate a GitHub Actions deployment workflow with Flyway Desktop
- Tutorial - Move from state to migrations-based deployments
- Connecting to production environments
- Executing scripts before or after deployment via callbacks
- Baselining your downstream environments
- Checking production environments for drift
- Tutorial - Drift Report for deployments using embedded snapshot
- Tutorial - Drift Report for deployments using snapshot files
- Tutorial - Resolve drift by incorporating it (migrations-based deployments)
- Tutorial - Resolve drift by incorporating it (state-based deployments)
- Tutorial - Resolve drift by reverting it
- Tutorial - Resolve drift by filtering it out
- Tutorial - Checking for drift in static data
- Reviewing deployment script ahead of deployment
- Generating a deployment changes report
- Running code review
- Implementing a roll back strategy
- Rolling out updates from a single schema to multiple production databases
- Integrate with Redgate Monitor
