ChangeTruncateTableWarn

This check warns a user when a table is being truncated so that they can ensure this change will not lead to unintentional data loss.

About ChangeTruncateTableWarn
Liquibase version required 4.6.0+
Scope (--checks-scope) changelog
Default status enabled
Default severity (exit code) 0 ("INFO")
Customizable settings No (static)

Uses

Use the check to warn when a table is being truncated, which is a significant database change which can destroy your organization’s most essential resource: critical data. Such an unintended change can result in permanent and irrecoverable data loss, production level service outages, and more. This policy check, like other checks, can be configured with a severity level which returns an exit code designed to stop automated jobs, giving your team time to inspect these significant changes.

Use ChangeTruncateTableWarn

Note: ChangeTruncateTableWarn only supports unmodeled changeset types. If you use this Policy Check with modeled changesets (XML, JSON, and YAML changelogs as well as all ChangeTypes except sql and sqlFile), a message will appear stating the changeset was skipped.

Prerequisites

  1. Ensure that you have correctly specified your Liquibase Pro license key.
  2. Ensure that the --checks-scope parameter includes the scope of this check.

For example:

--license-key=<string>
--checks-scope=<string>

Enable

This check is enabled by default. To verify that it is currently enabled, run the show command:

liquibase checks show --check-name=<string>

Customize

This check is static, meaning it does not have any customization settings.

Run

To run the check, use the run command:

liquibase checks run --check-name=<string>