DynamoDeleteGlobalSecondaryIndexCheck

Last updated: February 16, 2026

Alerts when changesets try to remove Global Secondary Indexes from DynamoDB tables, helping verify that deleting these indexes will not negatively impact query performance or break application functionality that depends on these alternative access patterns for retrieving DynamoDB data.

About DynamoDeleteGlobalSecondaryIndexCheck

Liquibase version required

4.31.0+

Scope (--checks-scope)

changelog

Default status

disabled

Default severity (exit code)

0 ("INFO")

Customizable settings

Yes (dynamic)

Prerequisites

Uses

Use this check to enforce the use of the Dynamo-specific DynamoDeleteGlobalSecondaryIndexCheck changetype. For example, you can:

  • Ensure specific changesets include the DynamoDeleteGlobalSecondaryIndexCheck changetype.

  • Warns or blocks deployments if the DynamoDeleteGlobalSecondaryIndexCheck changetype exists in any particular XML, YAML, or JSON changeset.

Procedure

1

This check is disabled by default. To enable it, run the enable command:

liquibase checks enable --check-name=DynamoDeleteGlobalSecondaryIndexCheck

You will see this output: Check 'DynamoDeleteGlobalSecondaryIndexCheck' has been enabled. +---------------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+ | Short Name                            | Scope     | Type   | Status  | Severity | Customization | Description                    | +---------------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+ | DynamoDeleteGlobalSecondaryIndexCheck | changelog | sql,   | enabled | 0        | <None>        | This check triggers when a     | |                                       |           | xml,   |         |          |               | XML,YAML, or JSON changeset    | |                                       |           | yaml,  |         |          |               | contains the Dynamo-specific   | |                                       |           | json   |         |          |               | deleteGlobalSecondaryIndex     | |                                       |           |        |         |          |               | changetype.                    | +---------------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+ Liquibase command 'checks enable' was executed successfully.

2

To set the severity of this check, run:

liquibase checks customize --check-name=DynamoDeleteGlobalSecondaryIndexCheck
3

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)

Results

You will see this output and the Severity you selected reflected in the Severity column. Your check will be enabled and customized successfully.

Customization complete. Review the table below to confirm your changes. +---------------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+ | Short Name                            | Scope     | Type   | Status  | Severity | Customization | Description                    | +---------------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+ | DynamoDeleteGlobalSecondaryIndexCheck | changelog | sql,   | enabled | 1        | <None>        | This check triggers when a     | |                                       |           | xml,   |         |          |               | XML,YAML, or JSON changeset    | |                                       |           | yaml,  |         |          |               | contains the Dynamo-specific   | |                                       |           | json   |         |          |               | deleteGlobalSecondaryIndex     | |                                       |           |        |         |          |               | changetype.                    | +---------------------------------------+-----------+--------+---------+----------+---------------+--------------------------------+ Liquibase command 'checks customize' was executed successfully.