Applies to:
- Liquibase Pro
- Liquibase Open Source (Community)
Summary:
When running policy checks, the file liquibase.checks-settings.conf
is used to determine which checks are enabled to run and which checks are available.
When new policy checks are added to Liquibase, the liquibase.checks-settings.conf
generated from another version of Liquibase will need to be updated.
For example, if you use the liquibase.checks-settings.conf
file generated from v4.27.0, it will not have the policy check maxAffectedRowsAllowedUpdate as it was released in v4.28.0.
Environment Conditions:
- Liquibase v4.12+
How to update the Liquibase checks file
When upgrading to a newer version of Liquibase and running any checks command in the CLI, a prompt will appear to update the liquibase.checks-settings.conf
file, which provides the option to update, not update, or skip.
If you have liquibase.command.autoUpdate=off
set, the prompt will not occur.
If you attempt to customize the policy check that isn't in the liquibase.checks-settings.conf
file, you will get an error:
Check appears to be configurable but cannot be located in the check settings configuration file.
Outside a pipeline:
If the liquibase.checks-settings.conf
exists outside the pipeline, set liquibase.command.autoUpdate=on and run a checks command. Follow the prompt to update the checks file.
Inside a pipeline:
If the liquibase.checks-settings.conf
is inside a pipeline/repo, the new version of the file will need to be generated outside of the pipeline and then added to the pipeline/repo in order to have access to the new checks inside the liquibase.checks-settings.conf
file.
Related Article(s):
N/A
Comments
0 comments
Article is closed for comments.