feat(configurator): delete.sh flow (v20.6.0)

[hyunsies]

Summary

New fourth configurator mode — Delete existing deployment. Generates delete.sh that cleanly removes MAP Auto-Tagger deployments in the selected region. MINOR bump; runtime YAML byte-identical to v20.5.4 except for four version stamps.

Implements items 2, 4, 5, 6, 8 of Jin's Wave-0 scope (aws-samples PR #27). Items 1 and 3 already shipped as PRs #47 and #48a; item 7 N/A on current main.

Flow

Three steps: Configure → Review → Download (same pattern as Deploy / Editor / Upgrade tabs).

Default: delete every map-auto-tagger-mig* Stack and StackSet in the region. Opt-in checkbox scopes to specific MPE(s).

Output filename:

• delete-all.sh by default
• delete-<mpe>-<mpe>.sh when scoped

Confirmation: type DELETE (uppercase) — works for both paths.

Script behavior

• Enumerates map-auto-tagger-mig* Stacks and StackSets in region
• StackSets: delete-stack-instances in parallel (100% tolerance), 30-min wait ceiling, then delete-stack-set
• Stacks: delete-stack + wait stack-delete-complete
• S3 staging bucket auto-map-tagger-\${ACCOUNT}: auto-decided — retained if any other map-auto-tagger-mig* deployment remains in the region (sibling-safe), deleted otherwise
• Optional: delete matching CloudWatch Log Groups (opt-in, default off — audit history retained)
• Never deletes: map-migrated tags on AWS resources (MAP credits remain intact), StackSet admin/execution IAM roles (shared org scaffolding)
• Legacy pre-namespacing probe: if no map-auto-tagger-mig* match and an unnamespaced map-auto-tagger stack exists, emits manual-delete instructions instead of silent exit (same pattern as upgrade.sh v20.5.4)
• Idempotent: missing resources are reported as skipped; non-zero exit only on real failures

Accepted limits

• Bucket race. Two simultaneous scoped deletes could each see the other's stack and both retain the bucket. Same class as §1.108 TOCTOU; accepted.
• No dry-run mode. Idempotency + typed confirmation are the dry-run equivalent.
• No pre-delete scope-overlap preflight. PR feat: Q3 Option D — scope-intersection preflight (§1.108) #38 protects the other direction.

Follow-ups tracked

• E2E harness for delete.sh ships as PR #48c (Sprint 7 P3 mandate). Separating keeps #48b reviewable.
• MPE-ID regex uses permissive ^mig[a-zA-Z0-9]+$ (matches Lambda runtime). Will tighten to ^mig[a-z0-9]{10}$ when H6 product call lands repo-wide.
• i18n: English-only for new keys (ui_mode_delete_title, ui_delete_*, err_delete_*); 7 non-English locales fall back to English via existing t() behavior. Translation follow-up (same pattern as ui_update_confirm_risk / ui_upgrade_*).

Supersedes

Jin's PR #27 (commits b034c93 adding destroy-flow + a392cea renaming destroy→delete). Re-anchored against post-#33/#35/#37/#38/#44 main; uppercase DELETE confirmation (item 8); permissive MPE regex to match Lambda; legacy-stack probe added.

Test plan

• Layer 1 local: sync-check, lint_cfn_correctness, lint_event_prefixes, lint_shell_injection, HTML well-formed, YAML Lambda py_compile, cfn-lint
• Template literal renders cleanly via Node — both variants (delete-all and scoped). Rendered scripts pass bash -n.
• Layer 1 CI (auto on PR)
• Manual: open configurator.html in browser → Delete tab → scope-all path (confirm filename delete-all.sh) → scope-to-MPE path (confirm filename includes MPEs)
• Layer 2 E2E on main (end-of-sprint dispatch) — covers PR #48a + #48b together
• PR #48c follow-up: add Test delete.sh generation and execution to the harness

Co-authored-by: Jin Shan Ng (aws-samples PR #27 Wave-0 scope).

🤖 Generated with Claude Code