@go-to-k/cdkd 0.33.0 → 0.35.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
@@ -175,7 +175,7 @@ the full per-type table.
175
175
 
176
176
  - **Node.js** >= 20.0.0
177
177
  - **AWS CDK Bootstrap**: You must run `cdk bootstrap` before using cdkd. cdkd uses CDK's bootstrap bucket (`cdk-hnb659fds-assets-*`) for asset uploads (Lambda code, Docker images). Custom bootstrap qualifiers are supported — CDK embeds the correct bucket/repo names in the asset manifest during synthesis.
178
- - **AWS Credentials**: Configured via environment variables, `~/.aws/credentials`, or `--profile` option
178
+ - **AWS Credentials**: Configured via environment variables, `~/.aws/credentials`, `--profile`, or `--role-arn` option. **The credentials must have admin-equivalent permissions for the resources being deployed.** Unlike `cdk deploy`, cdkd does NOT route through CloudFormation, so there is no cfn-exec-role to delegate to — every IAM / EC2 / Lambda / etc. API call is issued from cdkd directly. CDK CLI's `cdk-hnb659fds-deploy-role-*` only carries CFn + asset-publish permissions and is therefore NOT sufficient for cdkd. See `--role-arn` in [docs/cli-reference.md](docs/cli-reference.md) for assuming a role with the right permissions.
179
179
 
180
180
  ## Installation
181
181
 
@@ -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