Class TestSystemUpCommand
java.lang.Object
liquibase.command.AbstractCommandStep
liquibase.extension.testing.testsystem.command.TestSystemUpCommand
- All Implemented Interfaces:
CommandStep
-
Field Summary
Modifier and TypeFieldDescriptionstatic final CommandArgumentDefinition<Boolean>
static final String[]
static final CommandArgumentDefinition<String>
static final CommandArgumentDefinition<String>
static final CommandArgumentDefinition<String>
Fields inherited from class liquibase.command.AbstractCommandStep
coreBundle
Fields inherited from interface liquibase.command.CommandStep
ORDER_DEFAULT, ORDER_NOT_APPLICABLE
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionString[][]
Defines new command names For example, if it is part of `liquibase update`, this should return new String[][]{ new String[] {"update"}}.void
run
(CommandResultsBuilder resultsBuilder) Performs the business logic.Methods inherited from class liquibase.command.AbstractCommandStep
adjustCommandDefinition, getOrder, providedDependencies, requiredDependencies, validate
-
Field Details
-
COMMAND_NAME
-
NAME
-
VERSION
-
PROFILES
-
ACCEPT_LICENSES
-
-
Constructor Details
-
TestSystemUpCommand
public TestSystemUpCommand()
-
-
Method Details
-
defineCommandNames
Description copied from interface:CommandStep
Defines new command names For example, if it is part of `liquibase update`, this should return new String[][]{ new String[] {"update"}}. If it is a part of `liquibase example init`, this should return {"example", "init"}.This is used to determine the available command names.
This can return null if this step is not defining a new command but "cross-cutting" existing commands
-
run
Description copied from interface:CommandStep
Performs the business logic. This method should not be called directly. It is called by the overall pipeline logic in theCommandScope.execute()
order.- Throws:
Exception
-