@go-to-k/cdkd 0.236.0 → 0.238.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
@@ -161,9 +161,10 @@ The installed binary is `cdkd`.
161
161
  > account before any other command will work — it creates the S3 state
162
162
  > bucket (`cdkd-state-{accountId}`) that cdkd uses to track deployed
163
163
  > resources, plus cdkd-owned asset storage for the region
164
- > (`cdkd-assets-{accountId}-{region}` bucket +
165
- > `cdkd-container-assets-{accountId}-{region}` ECR repo — skip with
166
- > `--no-assets`; see [`cdkd bootstrap`](docs/cli-reference.md#cdkd-bootstrap)).
164
+ > (by default a `cdkd-assets-{accountId}-{region}` bucket +
165
+ > `cdkd-container-assets-{accountId}-{region}` ECR repo — custom names via
166
+ > `--asset-bucket` / `--container-repo`, skip with `--no-assets`; see
167
+ > [`cdkd bootstrap`](docs/cli-reference.md#cdkd-bootstrap)).
167
168
  > This replaces `cdk bootstrap`, which cdkd does not require — see
168
169
  > [Prerequisites](#prerequisites).
169
170
 
@@ -242,6 +243,7 @@ cdkd publish-assets # synth + upload only (typical CI split)
242
243
  cdkd destroy MyStack
243
244
  cdkd orphan MyStack/MyBucket # drop one resource from state (AWS resource stays)
244
245
  cdkd force-unlock MyStack # clear stale lock from an interrupted deploy
246
+ cdkd gc --dry-run # reclaim unreferenced cdkd-owned assets (S3 + ECR)
245
247
 
246
248
  # Migrate between cdkd and CloudFormation
247
249
  cdkd import MyStack --yes # adopt existing AWS resources into cdkd state