Maven dropAll

dropAll drops all database objects owned by the user. dropAll will not drop functions, procedures, or packages for the community version of Liquibase. Functions, procedures, packages, and synonyms can only be dropped for Liquibase Pro supported objects.

Uses

dropAll is typically used when there is a need to prepare an environment schema to be identical to another environment schema. dropAll is useful in the developer and test environments to remove unwanted objects to reset the database to “empty”.

The command makes it easier to standardize another schema, compared to manually deleting the objects, or dropping and recreating the desired schema.

dropAll should not be used in a production environment to prevent removal of required objects.

Maven configuration

Liquibase Maven can be configured in multiple ways. One way is to define your Liquibase configuration properties in your pom.xml file. To configure your pom.xml file, refer to Configuring Liquibase Attributes in your Maven POM File.

Running the dropAll Maven goal

Running the dropAll goal requires a Maven project to be implemented.

To run the goal, type the following in your command prompt:

mvn liquibase:dropAll

Using the dropAll goal with Liquibase Hub

If you use Liquibase Hub and want to receive the dropAll operation reports, you need to specify one of the following attributes when running the dropAll goal.

Attribute Definition Requirement
--hubConnectionId The attribute that identifies the specific Connection in which to record your data at Liquibase Hub. The attribute is available in your Project at https://hub.liquibase.com. The attribute is required only for the Liquibase Hub reporting
--hubProjectId The attribute that identifies the specific Project in which to record your data at Liquibase Hub. The attribute is available in your account at https://hub.liquibase.com. The attribute is required only for the Liquibase Hub reporting
--changeLogFile A registered changelog file that identifies the specific Project in which to record your data at Liquibase Hub. The attribute is optional to run the dropAll goal. If you specify a Liquibase Hub registered changelog, it will enable Liquibase Hub reporting.

Additionally, you need to be a Liquibase Hub user with a Liquibase Hub API Key set in the liquibase.properties or pom.xml file:

liquibase.properties example

liquibase.hub.apiKey: <HubAPIKey>
liquibase.hub.connectionId: <connectionId>
liquibase.hub.projectId: <projectId>

pom.xml example

<!-- Hub Mode -->
<hub.apiKey>HUB API KEY</hub.apiKey>
<hubConnectionId>CONNECTION ID</hubConnectionId>
<hubProjectId>PROJECT ID</hubProjectId>

You can also set your properties as Liquibase Environment variables:

LIQUIBASE_HUB_API_KEY="<HubAPIKey>"
LIQUIBASE_COMMAND_HUB_PROJECT_ID="<projectId>"
LIQUIBASE_COMMAND_HUB_CONNECTION_ID="<connectionId>"

Note: To retrieve or manage your API keys, go to API Keys by selecting your account in the upper-right corner of the page. To find the hubProjectId, select Projects > View Details. To find the hubConnectionId, select Project > View Details > Connections > View Status.

dropAll optional Maven configuration attributes

Attribute Definition
liquibase.changelogCatalogName Specifies the catalog Liquibase will use to create your changelog tables.
liquibase.changelogSchemaName Specifies the schema Liquibase will use to create your changelog tables.
liquibase.clearCheckSums [boolean] Forces checksums to be cleared from the DATABASECHANGELOG table. Default value is: false.
liquibase.databaseChangeLogLockTableName Specifies the table name to use for the DATABASECHANGELOGLOCK table.
liquibase.databaseChangeLogTableName Specifies the table name to use for the DATABASECHANGELOG table.
liquibase.databaseClass Specifies the database object class.
liquibase.defaultCatalogName Specifies the default catalog name to use for the database connection.
liquibase.defaultSchemaName Specifies the default schema name to use for the database connection.
liquibase.driver Specifies the driver class name to use for the database connection.
driverPropertiesFile Specifies the location of a JDBC connection-properties file which contains properties the driver will use.
liquibase.emptyPassword [boolean] Deprecated. Use an empty or null value for the password instead. Default value is: false
expressionVariables Specifies a map-based collection of your changelog properties to apply.
expressionVars Specifies a property-based collection of your changelog properties to apply.
liquibase.includeArtifact [boolean] Includes a Maven project artifact in the class loader which obtains the liquibase.properties file and your changelog files. Default value is: true.
liquibase.includeTestOutputDirectory [boolean] Includes the Maven test output directory in the class loader which obtains the liquibase.properties file and changelog files. Default value is: true.
liquibase.liquibaseProLicenseKey Specifies your Liquibase Pro license key.
liquibase.outputDefaultCatalog [boolean] Specifies whether to ignore the catalog/database name. Default value is: false.
liquibase.outputDefaultSchema [boolean] Specifies whether to ignore the schema name. Default value is: false.
liquibase.outputFileEncoding Indicates that you want to set the character encoding of the output file during the updateSQL phase.
liquibase.password Specifies the database password for the database connection.
liquibase.promptOnNonLocalDatabase [boolean] Controls whether users are prompted before executing changesets to a non-local database. Default value is: true.
liquibase.propertyFile Specifies the liquibase.properties you want to use to configure Liquibase.
liquibase.propertyFileWillOverride [boolean] Indicates that you want the liquibase.properties file to override any settings provided in the Maven plugin configuration. By default, if a property is explicitly specified it is not overridden if it also appears in the properties file. Default value is: false.
liquibase.propertyProviderClass Specifies the property provider which must be a java.util.Properties implementation.
liquibase.schemas Specifies the schemas to be dropped. Comma-separated list.
liquibase.server Specifies the server ID in the Maven settings.xml to use when authenticating.
liquibase.skip [boolean] Specifies whether to skip running Liquibase. The use of this attribute is not recommended but can be used when needed. Default value is: false.
systemProperties Specifies a list of system properties you want to pass to the database.
liquibase.url Specifies the database URL you want to use to execute Liquibase.
liquibase.username Specifies the database username for the database connection.
liquibase.verbose [boolean] Controls the amount of output detail when you call the plugin. Default value is: false.