@go-to-k/cdkd 0.209.1 → 0.210.0

package/README.md

@@ -251,10 +251,11 @@ The Docker-backed commands above require Docker. Pass `--from-state`
 substitute deployed physical IDs into intrinsic-valued env vars /
 secrets / image URIs; without either, intrinsic values are dropped with
 a per-key warning (matches `sam local *`). The two flags are mutually
-exclusive. `start-cloudfront` is the partial exception: a
-CloudFront-Functions + S3-origin distribution serves entirely in-process
-(no Docker), and it carries cdk-local's `--from-cfn-stack` but not cdkd's
-`--from-state` (its factory lacks the state-provider seam — issue #766).
+exclusive. `start-cloudfront` carries both `--from-state` and
+`--from-cfn-stack` too (since cdk-local 0.128.0 / issue #766); a
+CloudFront-Functions + S3-origin distribution still serves entirely
+in-process (no Docker), while a Lambda Function URL origin runs via the
+RIE container.
 
 ### `local invoke`
 

package/dist/cli.js

@@ -50809,14 +50809,17 @@ function createLocalInvokeAgentCoreCommand() {
 * `--stack-region`) live in cdk-local's `addStartAgentCoreSpecificOptions` and
 * are auto-inherited.
 *
-* UNLIKE `start-cloudfront`, this command DOES bind deployed state: cdk-local's
-* factory accepts an `extraStateProviders` option (the same seam the
-* heavy-wrapper `cdkd local *` commands use), so cdkd threads its S3-backed
-* `--from-state` factory in via `cdkdExtraStateProviders` and layers the
-* cdkd-specific `--from-state` / `--state-bucket` / `--state-prefix` flags on
-* top of cdk-local's inherited `--from-cfn-stack` / `--stack-region` (issue
-* #766). The factory's internal `createLocalStateProvider` call picks cdkd's
-* `fromState` factory transparently when `--from-state` is passed.
+* Like `start-cloudfront` / `start-alb` / `start-service`, this command binds
+* deployed state through cdk-local's `extraStateProviders` seam: the factory
+* accepts an `extraStateProviders` option (the same seam those commands use), so
+* cdkd threads its S3-backed `--from-state` factory in via
+* `cdkdExtraStateProviders` and layers the cdkd-specific `--from-state` /
+* `--state-bucket` / `--state-prefix` flags on top of cdk-local's inherited
+* `--from-cfn-stack` / `--stack-region` (issue #766; the `start-agentcore`
+* factory carried the seam from the start, the `start-cloudfront` factory gained
+* it in cdk-local 0.128.0). The factory's internal `createLocalStateProvider`
+* call picks cdkd's `fromState` factory transparently when `--from-state` is
+* passed.
 *
 * The active cdkd embed config is re-handed to the factory so branding stays
 * cdkd: cdk-local's factory calls `setEmbedConfig(opts.embedConfig)`, and
@@ -50871,16 +50874,17 @@ function createLocalStartAlbCommand() {
 * binding a Function URL origin's backing Lambda + a deployed-S3 origin's bucket
 * name to deployed state) live in cdk-local and are auto-inherited.
 *
-* UNLIKE `start-agentcore` / `start-alb` / `start-service`, this command does
-* NOT thread cdkd's S3-backed `--from-state` source: cdk-local's
-* `CreateLocalStartCloudFrontCommandOptions` accepts only `embedConfig`, not the
-* `extraStateProviders` seam (the factory's internal `createLocalStateProvider`
-* calls pass no fourth argument). So `--from-state` / `--state-bucket` /
-* `--state-prefix` and `cdkdExtraStateProviders` threading are intentionally
-* absent here — start-cloudfront stays exempt from issue #766 until cdk-local
-* adds `extraStateProviders` to its start-cloudfront factory. Until then the
-* `--from-cfn-stack` flag (CloudFormation-backed deployed state) is the only
-* state source on this command.
+* As of cdk-local 0.128.0 (go-to-k/cdk-local#426 / #436) the start-cloudfront
+* factory accepts the `extraStateProviders` seam — the same one
+* `start-agentcore` / `start-alb` / `start-service` use — so cdkd now threads
+* its S3-backed `--from-state` factory in via `cdkdExtraStateProviders` and
+* layers the cdkd-specific `--from-state` / `--state-bucket` / `--state-prefix`
+* flags on top of cdk-local's inherited `--from-cfn-stack` / `--stack-region`
+* (issue #766). The factory's internal `createLocalStateProvider` calls pick
+* cdkd's `fromState` factory transparently when `--from-state` is passed, so a
+* Function URL origin's backing Lambda + a deployed-S3 origin's bucket name can
+* be bound to cdkd-managed state (after a prior `cdkd deploy`), not just to a
+* CloudFormation stack.
 *
 * The active cdkd embed config is re-handed to the factory so branding stays
 * cdkd: cdk-local's factory calls `setEmbedConfig(opts.embedConfig)`, and
@@ -50889,7 +50893,14 @@ function createLocalStartAlbCommand() {
 * cdk-local's `cdkl` defaults.
 */
 function createLocalStartCloudFrontCommand$1() {
-	return createLocalStartCloudFrontCommand({ embedConfig: getEmbedConfig() });
+	const cmd = createLocalStartCloudFrontCommand({
+		embedConfig: getEmbedConfig(),
+		extraStateProviders: cdkdExtraStateProviders
+	});
+	cmd.addOption(new Option("--from-state", "Read cdkd's S3 state for the target stack and substitute Ref / Fn::GetAtt / Fn::Sub / Fn::ImportValue / Fn::GetStackOutput intrinsics when binding a Lambda Function URL origin's backing Lambda and a deployed-S3 origin's bucket name. Mutually exclusive with --from-cfn-stack.").default(false));
+	cmd.addOption(new Option("--state-bucket <bucket>", "S3 bucket for --from-state. Falls back to CDKD_STATE_BUCKET env or cdk.json context.cdkd.stateBucket."));
+	cmd.addOption(new Option("--state-prefix <prefix>", "S3 key prefix for --from-state state files.").default("cdkd"));
+	return cmd;
 }
 
 //#endregion
@@ -52836,7 +52847,7 @@ function reorderArgs(argv) {
 async function main() {
 	installPipeCloseHandler();
 	const program = new Command();
-	program.name("cdkd").description("CDK Direct - Deploy AWS CDK apps directly via SDK/Cloud Control API").version("0.209.1");
+	program.name("cdkd").description("CDK Direct - Deploy AWS CDK apps directly via SDK/Cloud Control API").version("0.210.0");
 	program.addCommand(createBootstrapCommand());
 	program.addCommand(createSynthCommand());
 	program.addCommand(createListCommand());