Note: This is a Liquibase Pro command, so you need a Liquibase Pro License Key to use it.
Liquibase quality checks allow you to analyze your changelogs, changesets, and SQL for specific commands and patterns that require close review early in the development life cycle. This feature can be integrated into your build and deployment automation to prevent non-compliant changes from entering the pipeline.
Quality checks help you customize the types of checks to fit the needs of your organization and let you do the following:
- Better secure your database by getting immediate notice that user and role privileges are being modified.
- Prevent data loss and corruption.
- Enforce internal standards and best practices to ensure that only high-quality, compliant changes are added to your projects.
- Quickly, consistently, and easily validate your changes from the local development environments.
- Integrate checks into automated workflows to provide quality gates for database changes in automation.
Quality checks have been tested for Oracle, SQL Server, PostgreSQL, MySQL, and MariaDB, but may be compatible with any relational database supported by Liquibase.
Quality Checks have three components
- The static and dynamic checks.
Learn more about static and dynamic checks here: List of Quality Checks
checkscommand and sub-commands
- The checks settings file that defines the configurations and parameters
All checks work in the command line and in automation. The command line is interactive and allows the configuration of dynamic checks.
Implementing Quality Checks
Set up quality checks for your team
- Identify the Quality Checks desired by your team. List of Quality Checks
- Create a package of Quality Checks. Quality Checks Packages
Integrate quality checks into manual and automated deployments
- Test quality checks in the CLI by using Subcommands. Quality Checks Commands
- Integrate Quality Checks into your automation process. Use Quality Checks in Automation: Severity and Exit Code