What parameters can I use with operation reports?
Last updated: July 14, 2025
The following parameters can be used with all operation reports. This includes the checks, drift, update, and rollback reports.
Parameters
Global parameters
Use these parameters to control the behavior of all operation reports.
Parameter | Type | Description | Requirement |
| Boolean | Enables or disables all reports at the global level. Overridden by | Required (either this or |
| String | Specifies the name of the report file at the global level. Overridden by | Optional |
| Boolean | Specifies whether to automatically open the report in your default browser at the global level. Overridden by | Optional |
| String | Specifies the file path to the report file at the global level. Overridden by | Optional |
| Boolean | Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from operation reports at the global level. Overridden by If If | Optional |
| Boolean | Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the global level. Overridden by | Optional |
Command parameters
Use these command parameters if you want to specify operation report behavior for a specific command.
When Liquibase detects database drift, it records that in your drift report. Use the --drift-severity
parameter to specify a severity return code (severity level) for all kinds of drift: changed, missing, or unexpected content. The severity return code you set tells Liquibase how to react when it detects drift. You can use the severity return code as an alert for the rest of your CI/CD pipeline.
BLOCKER
(4
): drift is a blocker (most severe)CRITICAL
(3
): drift is a critical errorMAJOR
(2
): drift is a major failureMINOR
(1
): drift is a minor failureINFO
(0
): drift is treated as an informational message (least severe)
If you want Liquibase to react to changed, missing, or unexpected content in different ways, you can set the individual --drift-severity-*
parameters to specify a severity return code for each particular kind of drift. These parameters take priority over --drift-severity
.
Parameter | Type | Description | Requirement |
| Boolean | Enables a report at the command level. Overrides the global parameter | Required (either this or |
| String | Specifies the severity level of all error types in the drift report (changed, missing, or unexpected content). Valid values are | Optional |
| String | Specifies the severity level of changed content in the drift report. Valid values are | Optional |
| String | Specifies the severity level of missing content in the drift report. Valid values are | Optional |
| String | Specifies the severity level of unexpected content in the drift report. Valid values are | Optional |
| String | Specifies the name of the report file at the command level. Overrides the global parameter | Optional |
| Boolean | If Note: Prior to Liquibase 4.29.0, this parameter was called | Optional |
| String | Specifies the file path to the report file at the command level. Overrides the global parameter | Optional |
| Boolean | Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter If If | Optional |
| Boolean | Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter | Optional |