pro-global-strip-comments-prioritized

--pro-global-strip-comments-prioritized is a global Boolean parameter. It specifies whether the --pro-global-strip-comments-prioritized parameter always takes priority over other Liquibase delimiter settings. It is available in Liquibase 4.29.2 and later and requires a valid Liquibase Pro license key to use. The default value is false.

Uses

You can set a delimiter in Liquibase in the following ways:

  1. stripComments set on a specific changeset, including in rollbackSqlFile (highest precedence)

  2. stripComments set in a changelog called by include or includeAll in modifyChangeSets

  3. --pro-global-strip-comments set globally (lowest precedence)

By default, --pro-global-strip-comments has the lowest precedence. This means that if you set it to false, and you set stripComments to true, Liquibase uses the value of stripComments anywhere there is a conflict.

However, if you want Liquibase to always strip comments based on --pro-global-strip-comments no matter what, you can set --pro-global-strip-comments-prioritized to true.

Syntax

You can set this parameter in the following ways:

Option

Syntax

Liquibase properties file (defaults file)

liquibase.pro.globalEndDelimiter.prioritized: <true|false>

Global flow file argument

globalArgs: { pro-global-end-delimiter-prioritized: "<true|false>" }

Global CLI parameter

liquibase --pro-global-end-delimiter-prioritized=<true|false> update --changelog-file=example-changelog.xml

JVM system property (JAVA_OPTS environment variable)

Unix:

JAVA_OPTS=-Dliquibase.pro.globalEndDelimiter.prioritized=<true|false>

Windows:

JAVA_OPTS=-D"liquibase.pro.globalEndDelimiter.prioritized"=<true|false>

Liquibase environment variable

LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>

For more information, see Working with command parameters.