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.

global-end-delimiter-override

Last updated: September 2, 2025

--global-end-delimiter-override is a global Boolean parameter. It lets you specify whether the --global-end-delimiter-override parameter always takes priority over other Liquibase delimiter settings. By default, it is set to 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.25.1 through 4.33, this parameter was called --pro-global-end-delimiter-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:

  • endDelimiter set on a specific changeset, including in rollbackSqlFile (highest precedence)

  • endDelimiter set in a changelog called by include or includeAll in modifyChangeSets

  • --global-end-delimiter-override set globally (lowest precedence)

By default, --global-end-delimiter-override has the lowest precedence. This means that if you set it to some value (such as @), and you set endDelimiter to a different value (such as &), Liquibase uses the value of endDelimiter as your delimiter anywhere there is a conflict.

However, if you want Liquibase to always set delimiters based on --global-end-delimiter-override no matter what, you can set --global-end-delimiter-override to true.

Syntax

You can set this parameter in the following ways:

Option

Syntax

Liquibase properties file (defaults file)

liquibase.globalEndDelimiter.override: <true|false>

Global flow file argument

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

Global CLI parameter

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

JVM system property (JAVA_OPTS environment variable)

Unix:

JAVA_OPTS=-Dliquibase.globalEndDelimiter. overrider=<true|false>

Windows:

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

Liquibase environment variable

LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>

For more information, see Working with command parameters.

Change history

Version

Change

Liquibase Secure, version 5.0

Parameter changed from --pro-global-end-delimiter-prioritized to --global-end-delimiter-override.

Here are the previous values from when it was --pro-global-end-delimiter-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>