What Liquibase commands are used for remote files?
Last updated: July 14, 2025
Note: Using Azure Blob Storage is available in Liquibase Pro 4.34.0 or later.
TESTING THE NOTE CARD.
Correct configuration of paths to locate files is vital to using Liquibase files remotely. The following tables provide high-level guidance to read or write remote Liquibase files.
Note: An output of log files to remote storage is not yet available.
File(s) | Commands | Example |
Generating a changelog (see below for calling a changelog in a command) |
| Relative changelog path required to preserve DBCL integrity. |
Flowfile (such as |
|
|
Checks settings file (such as |
|
|
Defaults file (such as | All |
|
Init project files changelog flow file liquibase.properties |
|
|
| All commands which support the |
|
| All that support the |
|
|
|
|
HTML operation report files | All that support Operation Reports |
|
Use relative path + searchpath for changelogs
File(s) | Commands | Example |
Using a changelog (changelog file/resources) SQL files include or includeAll files | update (all variants) rollback (all variants) changelog-sync status validate | liquibase --search-path=s3://myBucket update --changelog-file=changelogs/changelog.xml liquibase --search-path=az://myContainer update --changelog-file=changelogs/changelog.xml A relative changelog path is required to preserve the Liquibase tracking table integrity. |
Use searchpath with remote files
File(s) | Commands | Example |
Snapshots (such as | liquibase --search-path=s3://myBucket/mysnapshots diff --reference-url=offline:postgres?snapshot=mysnapshot.json liquibase --search-path=az://myContainer/mysnapshots diff --reference-url=offline:postgres?snapshot=mysnapshot.json | |
Native executor config files (such as | liquibase --search-path=s3://myBucket/configs update liquibase --search-path=az://myContainer/configs update There is no property to directly specify a native executor configuration file path. It is located using the |