@go-to-k/cdkd 0.50.13 → 0.51.1
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 +7 -5
- package/dist/cli.js +520 -111
- package/dist/cli.js.map +3 -3
- package/dist/go-to-k-cdkd-0.51.1.tgz +0 -0
- package/dist/index.js +164 -26
- package/dist/index.js.map +2 -2
- package/package.json +1 -1
- package/dist/go-to-k-cdkd-0.50.13.tgz +0 -0
package/README.md
CHANGED
|
@@ -314,11 +314,13 @@ cdkd drift MyStack --accept --yes
|
|
|
314
314
|
cdkd drift MyStack --revert --yes
|
|
315
315
|
|
|
316
316
|
# Refresh the deploy-time AWS snapshot used as drift baseline.
|
|
317
|
-
#
|
|
318
|
-
#
|
|
319
|
-
#
|
|
320
|
-
#
|
|
321
|
-
#
|
|
317
|
+
# Optional — `cdkd deploy` itself auto-refreshes on the first deploy after
|
|
318
|
+
# upgrading from a pre-v3 cdkd binary (= state schema `version: 2`), in
|
|
319
|
+
# parallel with the deploy at no critical-path cost. This command is the
|
|
320
|
+
# manual / non-deploy path: run it when you want the baseline refreshed
|
|
321
|
+
# without redeploying (e.g. for resources that won't change in any
|
|
322
|
+
# near-future deploy). Idempotent on the same v3 state — see "Drift
|
|
323
|
+
# detection" below for the full upgrade story.
|
|
322
324
|
cdkd state refresh-observed MyStack
|
|
323
325
|
|
|
324
326
|
# Dry run (plan only, no changes)
|