Runbook: Handle State Backend Size Limit

1 · Prerequisites

Confirm every item is in place before any state change.

• The state backend has a size limit
• The state is approaching the limit

2 · Pre-checks

Read-only diagnostic commands. If any of these don't match expected output, stop and investigate further.

• · The state size is approaching the limit
• · The backend has a size limit

3 · Procedure

Execute each step in order. Verify the expected output of a step before moving to the next.

1. 1Identify the state size
2. 2Split the state into smaller states
3. 3Apply the migration
4. 4Verify the plan is empty
5. 5Document the migration

4 · Verification

Confirm the procedure actually fixed the problem.

• ✓State is below the size limit
• ✓Plan is empty
• ✓Migration is documented

5 · Rollback

If verification fails, undo the procedure in reverse order.

• ↶If the split fails, restore the original state from a backup

6 · Escalation

When the runbook isn't enough, contact:

• · If the size limit is a recurring issue, escalate to the platform team