@go-to-k/cdkd 0.83.1 → 0.85.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.
package/README.md CHANGED
@@ -4,7 +4,7 @@
4
4
 
5
5
  - **Drop-in CDK compatible** — your existing CDK app code runs as-is.
6
6
  - **Up to 15x faster deploys than the AWS CDK CLI (CloudFormation)**
7
- - **Run AWS resources locally without deploying** — invoke Lambdas, serve API Gateway routes, and run ECS task definitions against Docker. SAM-compatible mental model, no `template.yaml` round-trip.
7
+ - **Run AWS resources locally without deploying** — invoke Lambdas, run ECS tasks, and serve API Gateway routes from Docker.
8
8
 
9
9
  ![cdkd demo](https://github.com/user-attachments/assets/0128730d-186d-4bd3-abea-aabc80ba4dd5)
10
10
 
@@ -395,6 +395,26 @@ modes (auto / selective / hybrid), `--resource-mapping` CDK CLI
395
395
  compatibility, CloudFormation migration flow, provider coverage, and the
396
396
  parity matrix vs upstream `cdk import`.
397
397
 
398
+ ## Exporting a stack back to CloudFormation
399
+
400
+ `cdkd export` is the mirror of `cdkd import`: it hands a cdkd-managed
401
+ stack over to CloudFormation via a CFn `ChangeSetType=IMPORT` changeset.
402
+ AWS resources are unchanged across the migration; cdkd state for the
403
+ exported stack is deleted on success. From then on the stack is managed
404
+ by `cdk deploy` / `aws cloudformation`.
405
+
406
+ ```bash
407
+ cdkd export MyStack # confirmation prompt; CFn stack name = cdkd stack name
408
+ cdkd export MyStack --cfn-stack-name MyStack-CFn
409
+ cdkd export MyStack --dry-run # print the import plan, do not call CFn
410
+ cdkd export MyStack --template path.json # skip synth, use a pre-rendered JSON template
411
+ ```
412
+
413
+ MVP scope: JSON templates only (CDK-generated). The command refuses to
414
+ proceed if any resource is not CFn-importable (Lambda-backed Custom
415
+ Resources, nested `AWS::CloudFormation::Stack` references); destroy or
416
+ accept abandoning those resources first.
417
+
398
418
  ## Drift detection
399
419
 
400
420
  `cdkd drift` (state-driven; no synth) compares each managed resource