tag command marks the current database state so you can roll back changes in the future.
tag command is typically used to mark the current database state, version, release, or any other information by adding the tag to the last row in the DATABASECHANGELOG table. After setting the tag, you can use the rollback command to roll back all changes up to that tag.
The image below shows the DATABASECHANGELOG table structure. Running the command
tag version1 applies the tag
version1 to the last row in the DATABASECHANGELOG table. If you run
rollback version1 command, it will roll back only
createTable C value.
Note: It is best practice to tag your changesets before running any other commands against your database.
To run the
tag command, specify the driver, classpath, and URL in the Liquibase properties file. For more information, see Create and Configure a liquibase.properties File. You can also specify these properties in your command line.
Then run the
liquibase tag version1
Note: Enter the name of the tag that you want to use in place of
version1. You don't need to specify the changelog file because the command marks the last row inserted in the DATABASECHANGELOG table regardless of what changelog file is specified.
tag 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.
The JDBC database connection URL
The database username
The database password
password attributes are not required for connections and systems which use alternate means of authentication.
tag command attributes
The tag identifying which tagged changesets in the changelog to evaluate.
Liquibase Community 4.9.1 by Liquibase Successfully tagged 'DBUSER@jdbc:h2:tcp://localhost:9090/mem:dev' Liquibase command 'tag' was executed successfully.