@go-to-k/cdkd 0.11.0 → 0.13.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)
@@ -429,6 +428,13 @@ cdkd destroy --all --force
 # Force-unlock a stale lock from interrupted deploy
 cdkd force-unlock MyStack
 
+# Inspect state-bucket info on demand (bucket name, region, source, schema version, stack count).
+# Routine commands (deploy / destroy / etc.) no longer print the bucket banner by default —
+# pass --verbose to surface it in their debug logs, or use this subcommand for an explicit answer.
+cdkd state info
+cdkd state info --json        # JSON output for tooling
+cdkd state info --state-bucket my-bucket  # explicit bucket; reports Source: --state-bucket flag
+
 # List stacks registered in the cdkd state bucket
 cdkd state list
 cdkd state ls --long          # include resource count, last-modified, lock status
@@ -447,8 +453,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 |