aws/aws-cdk

cdk: Destroy reports success when there is nothing to destroy

Open

#22,240 opened on Sep 26, 2022

View on GitHub
 (6 comments) (1 reaction) (0 assignees)TypeScript (3,530 forks)batch import
effort/smallfeature-requestgood first issuep3package/tools

Repository metrics

Stars
 (10,710 stars)
PR merge metrics
 (Avg merge 14d 11h) (68 merged PRs in 30d)

Description

Describe the bug

Configure AWS profile to an account that has not been bootstrapped with cdk. Run cdk destroy - cdk reports success.

Expected Behavior

cdk should report an error indicating that the selected stack does not exist.

Current Behavior

cdk incorrectly reports success in destroying the stack.

Reproduction Steps

Create a stack, switch accounts. execute: cdk destroy

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.43.1 (build c1ebb85)

Framework Version

No response

Node.js Version

v16.16.0

OS

MacOS Monterey

Language

Typescript

Language Version

Actually, javascript but drop down does not offer that option

Other information

No response

Contributor guide

Research direction
Investigate the CDK destroy command to identify why it returns success when no stack exists. Look at the logic that checks for stack existence before destruction.
Tech stack
typescript
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75