- Task
- Version · 6.0
- Create
Use search-path to locate changelogs on Azure
Last updated: August 11, 2026
Both a directory in the search path and a relative path are required to find changelog files or snapshot files. Follow the steps below to learn how to set both of these and configure them.
Procedure
Determine the paths necessary to locate the changelog to use.
If changelog resources, such as additional included changelogs or SQL files are in a different path, you will have multiple items in the searchpath.
If a changelog file is in Azure Blob Storage at az://myContainer/demo and the SQL files referenced by the changelog are in az://myContainer/demo/sqlFiles, your search path is az://myContainer/demo,az://myContainer/demo/sqlFiles.
Provide the searchpath and a filename or relative path to the changelogfile in remote storage.
Example 1: update-sql command using a changelog file in remote storage:
liquibase --search-path=az://myContainer/demo,az://myContainer/demo/sqlFiles update-sql --changelog-file=example-changelog.sql liquibase --search-path=az://myContainer/demo update-sql --changelog-file=example-changelog.sql
Example 2: update-sql command using a relative path to the changelog file in remote storage:
If the changelog is located in a subdirectory like az://myContainer/demo/changelogs, when you use the searchpath defined in the previous example, then you must specify the relative path to the changelog:
liquibase --search-path=az://myContainer/demo,az://myContainer/demo/sqlFiles update-sql --changelog-file=changelogs/example-changelog.sql
Note: Paths to changelogs must always be relative to preserve integrity of the Liquibase DATABASECHANGELOG tracking table.