As organizations strive for faster deployment cycles and improved collaboration, building out automation becomes essential for achieving a successful Liquibase implementation.
By automating repetitive database tasks and streamlining workflows, teams can enhance efficiency, reduce errors, and focus on delivering value to their customers.
Liquibase Pro Flow makes automating consistent database change management easy, no matter what databases or tools your teams are using. By defining one or more workflows, release teams can enforce standard database management processes and policies independently of database or pipeline vendor.
These YAML-based workflows are known as flow files or flows. Flow files can contain Liquibase commands, shell commands, and calls to external shell scripts. Flows can even call other flows.
Use these sample flow files to help build your automation framework. These flows include workflows for automating database scenarios such as premerges, deployments, postmerges, and rollbacks. This implementation guide also provides examples for calling Liquibase Pro Flows with GitHub Actions and Azure DevOps.
It is best practice to house Liquibase Flows in a centralized repository. A centralized repository with read-only access for application development teams will help enforce workflow governance and maintain database deployment consistency across the organization.
Configure your automation tool or Operation Reports from these guides: