@go-to-k/cdkd 0.148.0 → 0.149.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +13 -6
  2. package/dist/cli.js +18585 -18488
  3. package/dist/cli.js.map +1 -1
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -316,7 +316,9 @@ cdkd state resources MyStack --json # full JSON array
316
316
 
317
317
  # Show full state record for a stack (metadata, outputs, all resources incl. properties)
318
318
  cdkd state show MyStack
319
- cdkd state show MyStack --json # raw {state, lock} JSON
319
+ cdkd state show MyStack --json # raw {state, lock} JSON
320
+ cdkd state show MyParent --show-nested # recursively show every nested-stack child (#555 A4)
321
+ cdkd state show MyParent --show-nested --json # tree as nested {state, lock, children: [...]} JSON
320
322
 
321
323
  # Orphan one or more RESOURCES from cdkd's state (does NOT delete AWS resources).
322
324
  # Per-resource, mirrors aws-cdk-cli's `cdk orphan --unstable=orphan`.
@@ -587,11 +589,16 @@ the offending resources (or accept abandoning them) first. Nested
587
589
  [#464](https://github.com/go-to-k/cdkd/issues/464) PR B1: `cdkd export`
588
590
  recursively walks the cdkd state tree, validates every parent → child
589
591
  link, and surfaces the full leaf-first migration scope to the user;
590
- the CFn-side `--include-nested-stacks` IMPORT changeset submission
591
- itself is deferred to PR B2, so the command warns on `--dry-run` /
592
- hard-errors on real run with a clear pointer + workaround (keep on
593
- cdkd, or destroy children leaf-first via `cdkd state destroy <child>`
594
- and re-export the flattened parent). Fresh `cdkd deploy` of nested
592
+ the CFn-side per-stack IMPORT loop submission itself is deferred to
593
+ PR B2 (the original "one atomic `--include-nested-stacks` IMPORT
594
+ changeset" design was found infeasible by the 2026-05-24 AWS spike
595
+ AWS rejects that flag combination with
596
+ `ValidationError: IncludeNestedStacks is not supported for changeSet type: IMPORT`;
597
+ see [docs/design/464-nested-stacks-export-import.md](docs/design/464-nested-stacks-export-import.md)
598
+ §4.0), so the command warns on `--dry-run` / hard-errors on real run
599
+ with a clear pointer + workaround (keep on cdkd, or destroy children
600
+ leaf-first via `cdkd state destroy <child>` and re-export the
601
+ flattened parent). Fresh `cdkd deploy` of nested
595
602
  stacks works via [#459](https://github.com/go-to-k/cdkd/issues/459).
596
603
 
597
604
  ```bash