changelog-sync command marks all undeployed changes in your changelog as executed in your database.
changelog-sync command is typically used when you want to baseline a new database environment.
An example use case for the
changelog-sync command is when you have a DEV environment with a set of objects used only in DEV, and you want to use the same changelog to manage a new TEST environment.
The TEST environment does not have or need, those DEV-only objects. To avoid deploying the DEV-only objects, you run the
changelog-sync command to mark those changes as executed in the DATABASECHANGELOG which tells Liquibase to treat these databases as equivalent.
You can also use the
changelog-sync command to mark a change as executed if the object associated with the change was created manually on the database. By marking the changeset as executed, it prevents the next Liquibase update from failing as it tries to create an object that already exists.
To run the
changelog-sync command, specify the driver, classpath, and URL in Liquibase properties file. For more information, see Specifying Properties in a Connection Profile. You can also specify these properties in your command line.
Then run the
liquibase --changelog-file=mychangelog.postgresql.sql changelog-sync
Note: Enter the name of the changelog that you want to use in place of
changelog-sync global attributes
||The root changelog||Required|
||The JDBC database connection URL||Required|
||The database username||Required*|
||The database password||Required*|
password attributes are not required for connections and systems which use alternate means of authentication.
changelog-sync example output
When successful, the
changelog-sync command produces the following output:
Liquibase Pro 3.9.0 by Datical licensed to Liquibase Pro Customer until Tue Sep 22 19:00:00 CDT 2020 postgres@jdbc:postgresql://localhost:5432/MYDATABASE2 is up to date Liquibase command 'changelog-sync' was executed successfully.