New Webinar: Govern roles, shares, and data movement in Snowflake

Learn how to govern Snowflake roles, shares, and data movement without slowing delivery. Join our live webinar on controlling drift, permissions, and audit readiness.

Save your spot

global-strip-comments-override

Last updated: September 2, 2025

--global-strip-comments-override is a global Boolean parameter. It specifies whether the --global-strip-comments-override parameter always takes priority over other Liquibase delimiter settings. The default value is false.

It is available in Liquibase Secure 5.0 and later and requires a valid Liquibase Secure license key to use.

From Liquibase Pro version 4.29.2 through 4.33, this parameter was called --pro-global-strip-comments-prioritized. See the change history table at the end of this article for pre-5.0 version syntax.

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. --global-strip-comments set globally (lowest precedence)

By default, --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 --global-strip-comments no matter what, you can set --global-strip-comments-override to true.

Syntax

You can set this parameter in the following ways:

Option

Syntax

Liquibase properties file (defaults file)

liquibase.globalStripComments.override: <true|false>

Global flow file argument

globalArgs: { global-strip-comments-override: "<true|false>" }

Global CLI parameter

liquibase --global-strip-comments-override=<true|false> update --changelog-file=example-changelog.xml

JVM system property (JAVA_OPTS environment variable)

Unix:

JAVA_OPTS=-Dliquibase.globalStripComments.override=<true|false>

Windows:

JAVA_OPTS=-D"liquibase.globalStripComments.override"=<true|false>

Liquibase environment variable

LIQUIBASE_GLOBAL_STRIP_COMMENTS_OVERRIDE=<true|false>

For more information, see Working with command parameters.

Change history

Version

Changes

Liquibase Secure, version 5.0

Parameter changed from --pro-global-strip-comments-prioritized to --global-strip-comments-override.

Here are the previous values from when it was --pro-global-strip-comments-prioritized.

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>