@go-to-k/cdkd 0.11.0 → 0.12.0

package/README.md

@@ -407,7 +407,6 @@ cdkd deploy -c env=staging -c featureFlag=true
 cdkd deploy MyStack \
   --app "npx ts-node app.ts" \
   --state-bucket my-cdkd-state \
-  --region us-east-1 \
   --verbose
 
 # Show diff (what would change)
@@ -447,8 +446,20 @@ cdkd state show MyStack --json        # raw {state, lock} JSON
 cdkd state rm MyStack                 # confirmation prompt (y/N)
 cdkd state rm MyStack --yes           # skip confirmation
 cdkd state rm StackA StackB --force   # also bypass the locked-stack refusal
+
+# Destroy a stack's AWS resources AND remove its state record, without
+# requiring the CDK app (no synth — works from any working directory).
+cdkd state destroy MyStack            # per-stack confirmation prompt
+cdkd state destroy MyStack OtherStack --yes
+cdkd state destroy --all -y           # every stack in the bucket
+cdkd state destroy MyStack --region us-east-1
 ```
 
+> `cdkd state destroy` vs `cdkd state rm`: `state destroy` deletes both the
+> AWS resources and the state record (the equivalent of `cdkd destroy` minus
+> the CDK-app dependency). `state rm` only forgets the state record and
+> leaves the AWS resources intact.
+
 ### Concurrency Options
 
 | Option | Default | Description |