- Reference
- Version ยท 6.0
- Change Automation Reference
quiet
Last updated: September 29, 2026
The --quiet parameter is a shortcut for --verbosity=quiet. It prints the results payload only, omitting the banner, the license line, changeset headers and comments, summaries, and the trailing confirmation messages, and it lowers the log level to SEVERE.
The results payload is never suppressed. For example, update-sql --quiet still prints the generated SQL.
The --quiet default value is false.
Uses
Use --quiet when you want the shortest way to reduce a command to its payload, typically when the output is piped into another tool or captured by a CI job. It is equivalent to passing --verbosity=quiet, so reach for --verbosity instead when you want to select a tier explicitly or switch between tiers.
Using the --quiet parameter
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.
--quiet is an optional parameter that is either set in the Liquibase properties file or specified on the command line. The value specified on the command line overrides the value set in the properties file.
Note: If you set both --quiet and --verbosity, the explicitly set --verbosity wins. For example, --quiet --verbosity=verbose runs at the verbose tier.
Examples
liquibase --quiet update-sql --changelog-file=example-changelog.xml
Syntax
You can set this parameter in the following ways:
Option | Syntax |
|---|---|
Liquibase properties file (defaults file) |
|
Global flow file argument |
|
Global CLI parameter |
|
JVM system property (JAVA_OPTS environment variable) | Unix: |
Liquibase environment variable |
|
Using --quiet alongside --log-level
--quiet lowers the log level to SEVERE only when --log-level is not set. An explicitly set --log-level always wins.