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.

What is the liquibase.properties file?

Last updated: September 2, 2025

You can use a defaults file called liquibase.properties to store information that Liquibase needs to connect to a particular database, along with other properties that rarely change. This lets you avoid entering properties through your command line, saving you time and reducing errors.

Arguments that are entered at a command prompt override values that are specified in liquibase.properties.

Ways to create a liquibase.properties file

Liquibase comes preinstalled with example liquibase.properties files in the $LIQUIBASE_HOME/examples/<sql|xml|yaml|json> directories. By default, when you run a command, Liquibase looks for the liquibase.properties file in the directory Liquibase is running in.

There are three ways to create a defaults file:

  • You can automatically generate a liquibase.properties file by running the init project command to create a new Liquibase project.

  • You can also manually create a new text file in your project Liquibase directory and name it liquibase.properties.

  • You can specify a custom name and location for your defaults file by using the --defaults-file parameter. For more information, see Working with Command Parameters.

Example defaults file

The following example liquibase.properties file works for an Oracle database:

changelogFile: ../path/to/file/dbchangelog.xml
driver: oracle.jdbc.OracleDriver
url: jdbc:oracle:thin:@192.168.0.22:1521/orcl
referenceDriver: oracle.jdbc.OracleDriver
referenceUrl: jdbc:oracle:thin:@192.168.0.22:1521/orcl
licenseKey: aeioufakekey32aeioufakekey785463214
classpath: ../path/to/file/ojdbc6-11.2.0.3.0.jar
What is the liquibase.properties file? - Liquibase