The Flyway team are proud to announce the latest update to Flyway, the world’s most popular migrations framework for database deployments. Flyway v8.0 introduces three main areas of improvement, alongside bug fixes and breaking changes.
With the latest update we’re bringing the benefits of Flyway migrations into cloud native environments, such as Google Cloud Platform. Flyway is now compatible with Google BigQuery and Spanner, without any extra steps (currently in Beta, final release shortly).
Security and Identity
Secrets management, sensitive data protection, and identity and access control can now be part of the development stack. Flyway v8.0 deployments work with HashiCorp Vault, DAPR and AWS IAM, reducing the risk of security vulnerabilities, and ensuring audit compliance.
We’ve made Flyway significantly more flexible, to help you to make better choices about how you deploy in larger, more complex environments. Custom validation rules force Flyway to be more malleable around what’s a valid project state, unblocking those who need more flexibility. Environment-dependent script execution makes it possible to avoid building complex setups for each of your deployment targets, saving time and aggravation.
Flyway can now execute migrations written in shell scripting languages. Just as with SQL migrations, you can also write migrations in Python, Bash, and others. Finally, you can aggregate scripts with Baseline migrations to improve transparency and reduce the chances of errors.
Growing the value of Flyway
Many of the improvements above will only be available in our paid-for tier, Flyway Teams edition (and in Redgate Deploy). This is in keeping with our policy of improving and charging for Flyway Teams so that we can continue to commit to keeping Flyway Community free and open source.
Here’s a summary of the main feature improvements, and you can find the detailed documentation for the release on the Flyway site here.