status

The status command states the number of undeployed changesets. Running status lists all undeployed changesets. It also lists the id, author, and file path name for each undeployed changeset. The status command does not modify the database.

Uses

The status command is typically used when changesets were added to a changelog through source control by another developer. The command confirms what has been deployed and what changesets are pending per author and corresponding IDs.

Running the status command

To run the status command, specify the driver, classpath, and URL in the properties file. You can also specify these properties in your command line.

Run the status command:

liquibase --changelog-file=<changelog.xml> status

where <changelog.xml> represents the name of the changelog.

Note: Add the changelog-file to the Liquibase properties file to save time and reduce errors.

status global attributes

Tip: For best results, specify all commands and parameters in the --kebab-case format in the CLI. If your preference is camelCase, it also works in the CLI.

Atrributes Definition Requirement
--changelog-file

The root changelog

Required
--url

The JDBC database connection URL

Required
--username

The database username

Required
--password

The database password

Required

Note: The username and password attributes are not required for connections and systems which use alternate means of authentication.

status command attributes

Atrributes Definition Requirement
--verbose

Specify the detail level of the output.

Optional