EndDelimiterExistsWhenPatternExists

Last updated: July 14, 2025

This check triggers when the following criteria are met:

- A changeset contains the supplied pattern string or regex. - No end delimiter exists specifically in the changeset or via options such as the 'pro-global-end-delimiter' or 'endDelimiter' attribute set on a specific changeset and/or 'endDelimiter' set in a changelog called by include or includeAll in modifyChangeSets tag.

Uses

Property

Value

Liquibase version required

4.27.0+

Scope (--checks-scope)

changelog

Default status

disabled

Default severity (exit code)

0 ("INFO")

Customizable settings

Yes (dynamic)

Certain changesets need an end delimiter specifically set, while others do not need the end delimiter. This check makes sure changesets that require an end delimiter have one before moving forward in a job.

If a custom pattern exists in a changeset, then that changeset must have an enddelimiter. If the enddelimiter does not exist, this check notifies the user.

Before you begin

  1. Ensure that you have correctly specified your Liquibase Pro license key.

  2. Ensure that the --checks-scope parameter includes the scope of this check.

Changelog checks prerequisites

--license-key=<string>
--checks-scope=<string>

Procedure

1

Enable

This check is enabled by default. To verify that it is currently enabled, run the checks show command:

liquibase checks show --check-name=<string>

2

Customize

This check is dynamic, meaning you can customize its settings. See the table on this page for more information.

1. Once you've enabled the check, follow the steps in the CLI to set new values.

Default values are shown in[brackets]. You can use these by pressingEnter. Alternatively, specify custom values. If a customization setting does not have a default value, you must specify custom values.

2. When finished, verify that your configuration is correct by running thechecks showcommand.

liquibase checks show --check-name=<string>

3. If you need to make any other changes, run thechecks customizecommand:

liquibase checks customize --check-name=<string>

Note: If you want to create another variant of this check with different settings, use thechecks copycommand to create a copy of the original check and then use thechecks customizecommand to customize it.

3

Run

To run the check, use the checks run command.

liquibase checks run --check-name=<string>