PatternAFollowedByPatternB
The PatternAFollowedByPatternB
Policy Check triggers on changesets in which user-supplied regular expression pattern A is followed by the user-supplied regular expression pattern B. This check is pre-configured, so users only need to supply the patterns and do not have to manually write regular expressions to look ahead in their changelog.
Uses
The PatternAFollowedByPatternB
check can be used to confirm conditions within the changelog. This check allows you to check for specific patterns in your changelog and then produce a logged record of changeset structure when certain conditions are met. When it is executed successfully the checks message is logged to the console and logs as proof that changesets conform to specific standards.
Short Name | Scope | Enabled | Severity | Customization | Description |
---|---|---|---|---|---|
PatternAFollowedByPatternB
|
changelog |
false |
Default value: 0
|
<None> |
This check is pre-configured, so users only need to supply the patterns and do not have to manually write regular expressions to look ahead in their changelog. |
Run the PatternAFollowedByPatternB check
To run the PatternAFollowedByPatternB
check, ensure you have a Liquibase Pro license and the checks-scope
property includes changelog
. The checks-scope parameter is set in the default properties file, environment variable, or any standard method.
Tip: PatternAFollowedByPatternB
logic: If regular expression pattern X exists then Pattern A must exist after pattern X.
In this example, you are ensuring that all snapshot tables go into a dataset called IDW_BackUP. When this check runs successfully, a log will be created that displays all snapshot tables that are contained in the IDW_BACKUP dataset. First, ensure you have a Liquibase Pro license, a valid URL property
-
Enable the
PatternAFollowedByPatternB
check by running the following command in the CLI:liquibase checks enable --check-name=PatternAFollowedByPatternB
- Give your check a short name for easy identification such as
RegexLookAheadCheck
. The newRegexLookAheadCheck
check is created from thePatternAFollowedByPatternB
.Note: You can use up to 64 alpha-numeric characters in any short name.
-
In the CLI, set the Severity to return a code of 0-4 when the check is triggered. Set the severity to 0.
Your options are:'INFO'|0, 'MINOR'|1, 'MAJOR'|2, 'CRITICAL'|3, 'BLOCKER'|4)
-
Set the
'PRIMARY_SEARCH_STRING'
to a string or a valid regular expression.
Set it to a regular expression(ALTER|DROP)\s*TABLE
. -
Set the
'LOOKAHEAD_SEARCH_STRING'
to a string or a valid regular expression.
Set it to a regular expressionCREATE\s*SNAPSHOT\s*TABLE
. -
Set the case sensitivity to true or false.
Set it to'CASE_SENSITIVE' false
. -
Set the 'LOOKAHEAD_MESSAGE'.
Set it to'<LOOKAHEAD_SEARCH_STRING>'
must follow'<PRIMARY_SEARCH_STRING>'
-
Set the 'STRIP_COMMENTS' to
true
orfalse
.
Set it totrue
.Once successfully run, either of the two resulting reports appear:
CHANGELOG CHECKS ---------------- Checks completed validation of the changelog and found the following issues: Check Name: Pattern a followed by pattern b (RegexLookAheadCheck) Changeset ID: createFunction Changeset Filepath: changelog.sql Check Severity: MINOR (Return code: 1) Message: A match for regular expression 'PRIMARY_SEARCH_STRING' must be followed by 'LOOKAHEAD_SEARCH_STRING' was not detected in Changeset 'createFunction'.