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

databricks-http-path

Last updated: September 2, 2025

--databricks-http-path is a global parameter for the Liquibase Secure Databricks extension. It specifies the HTTP path of the compute resource (a Databricks cluster or a Databricks SQL warehouse) for Liquibase to use.

This parameter is hidden in Liquibase logs, even if --log-level is FINE. It is not exposed in the database connection URL. Instead, Liquibase uses it as a driver parameter.

It is available in the Liquibase Secure Databricks extension 1.0.0 and later.

Uses

You can use --databricks-http-path as an alternative to specifying your HTTP path directly in your Databricks connection URL.

If you don't specify --databricks-http-path, you must specify your HTTP path in your connection URL. For example:

jdbc:databricks://<server_hostname>:443;httpPath=/sql/1.0/warehouses/<your_warehouse_id>;

Syntax

You can set this parameter in the following ways:

Option

Syntax

Liquibase properties file (defaults file)

liquibase.databricks.httpPath: <string>

Global flow file argument (example)

stages: Default: actions: - type: liquibase command: update

globalArgs: { databricks-http-path: <string>" }

Global CLI parameter

liquibase --databricks-http-path=<string>update

--changelog-file=example-changelog.xml

JVM system property JAVA_Opts Environment Variable

Unix:

JAVA_OPTS=-Dliquibase.databricks.httpPath=<string>

Windows:

JAVA_OPTS=-D"liquibase.databricks.httpPath"=<string>

Liquibase environment variables

LIQUIBASE_DATABRICKS_HTTP_PATH=<string>

For more information, see Working with Command Parameters.