feat(gen2-migration): implement decommission command with optimized stateful resource validation #14325
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes
This PR implements stateful resource validation for the decommission command in Gen2 migration. In the decommission command's validation section
(decommission.ts), we scan CloudFormation changesets to detect stateful resources (DynamoDB tables, S3 buckets, Cognito user pools, etc.) scheduled for deletion and prevent accidental data loss by blocking the operation.This PR also optimizes stateful resource validation
(_validations.ts)by implementing rate-limited concurrent API calls using Bottleneck to prevent CloudFormation throttling during nested stack scanning. UX improvements include spinner feedback with category-specific progress messages and enhanced error handling with retry logic.Issue #, if available
Description of how you validated changes
Checklist
yarn testpassesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.