DynamoDeleteDynamoTableCheck
Last updated: September 2, 2025
The DynamoDeleteDynamoTableCheck changelog check triggers when a XML, YAML, or JSON changeset contains the Dynamo-specific deleteDynamoTable change type.
About | |
|---|---|
Liquibase version required | 4.31.0+ |
Scope ( |
|
Default status |
|
Default severity (exit code) |
|
Customizable settings | Dynamic customization available |
Prerequisites
You must download the Liquibase AWS extension jar and save it to your
/libfolder.
Uses
Use this check to enforce the use of the Dynamo-specific deleteDynamoTable change type. For example, you can:
Ensure specific changesets include the
deleteDynamoTablechange type.Warn or block deployments if the
deleteDynamoTablechange type exists in any particular XML, YAML, or JSON changeset.
Procedure
This check is disabled by default. To enable it, run the enable command:
You will see this output:
Check 'DynamoDeleteDynamoTableCheck' has been enabled.
+------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+
| Short Name | Scope | Type | Status | Severity | Customization | Description |
+------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+
| DynamoDeleteDynamoTableCheck | changelog | sql, | enabled | 0 | <None> | This check triggers when a |
| | | xml, | | | | XML,YAML, or JSON changeset |
| | | yaml, | | | | contains the Dynamo-specific |
| | | json | | | | deleteDynamoTable changetype. |
+------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+
Liquibase command 'checks enable' was executed successfully.
To set the severity of this check, run:
Set the severity level. This determines the exit code when the check is triggered. Choose one:
INFO (0)
MINOR (1)
MAJOR (2)
CRITICAL (3)
BLOCKER (4)