@go-to-k/cdkd 0.34.0 → 0.36.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
@@ -282,6 +282,11 @@ cdkd deploy MyStack \
282
282
  # Show diff (what would change)
283
283
  cdkd diff MyStack
284
284
 
285
+ # Detect drift between cdkd state and AWS reality (state-only; no synth)
286
+ # Exits 0 with no drift, 1 when drift is detected, 2 on error.
287
+ cdkd drift MyStack
288
+ cdkd drift --all --json
289
+
285
290
  # Dry run (plan only, no changes)
286
291
  cdkd deploy --dry-run
287
292
 
@@ -371,6 +376,30 @@ cdkd state destroy MyStack --region us-east-1
371
376
  > `cdkd destroy` (synth-driven, deletes AWS resources + state) and
372
377
  > `cdkd state destroy` (state-driven, same effect) round out the matrix.
373
378
 
379
+ ## `publish-assets`: synth + build + publish, no deploy
380
+
381
+ `cdkd publish-assets` runs the asset half of the deploy pipeline only —
382
+ synthesize the CDK app, build any Docker images, upload file assets to
383
+ S3, push images to ECR — and stops. No state writes, no provisioning,
384
+ no lock acquisition. This is the typical CI split where one runner
385
+ builds and uploads assets and a separate runner deploys.
386
+
387
+ ```bash
388
+ cdkd publish-assets # synth + publish all stacks (or auto-detect single stack)
389
+ cdkd publish-assets MyStack # synth + publish a specific stack
390
+ cdkd publish-assets --all # synth + publish every stack in the app
391
+ cdkd publish-assets 'MyStage/*' # wildcard (CDK display path)
392
+ cdkd publish-assets -a cdk.out # skip synth — use a pre-synthesized cloud assembly
393
+ ```
394
+
395
+ Stack selection follows the same rules as `deploy` / `diff` / `destroy`
396
+ (positional > `--stack` > `--all` > auto-detect). Concurrency knobs
397
+ are `--asset-publish-concurrency` and `--image-build-concurrency`.
398
+ `-a/--app` accepts either a shell command (`"npx ts-node app.ts"`) or
399
+ a path to an already-synthesized cloud assembly directory; pointing at
400
+ `cdk.out` skips synthesis. See [docs/cli-reference.md](docs/cli-reference.md#publish-assets-synth--build--publish-no-deploy)
401
+ for details.
402
+
374
403
  ## `--no-wait`: skip async-resource waits
375
404
 
376
405
  CloudFront Distributions, RDS Clusters/Instances, ElastiCache, and