@go-to-k/cdkd 0.69.0 → 0.71.0

package/README.md

@@ -248,10 +248,12 @@ cdkd has three command families:
   use them to inspect / clean up state when the source is gone or
   you don't want to synth. `cdkd state destroy` is the CDK-app-free
   counterpart of `cdkd destroy`.
-- **`cdkd local ...` subcommands** (`local invoke`) run a synthesized
-  Lambda function locally inside a Docker container that bundles the
-  AWS Lambda Runtime Interface Emulator (RIE). No AWS API calls, no
-  state bucket needed.
+- **`cdkd local ...` subcommands** (`local invoke`, `local start-api`)
+  run synthesized Lambda functions locally inside Docker containers that
+  bundle the AWS Lambda Runtime Interface Emulator (RIE). `local invoke`
+  runs a single Lambda once; `local start-api` stands up a long-running
+  HTTP server that maps API Gateway / HTTP API / Function URL routes to
+  local Lambda invocations. No AWS API calls, no state bucket needed.
 
 Options like `--app`, `--state-bucket`, and `--context` can be omitted if configured via `cdk.json` or environment variables (`CDKD_APP`, `CDKD_STATE_BUCKET`).
 
@@ -585,6 +587,16 @@ Requires Docker. v1 supports Node.js and Python runtimes (`nodejs18.x` /
 `nodejs20.x` / `nodejs22.x` / `python3.11` / `python3.12` / `python3.13`);
 other runtimes follow in subsequent PRs.
 
+**Container Lambdas (PR 5 of #224)** — `lambda.DockerImageFunction(...)` /
+`Code.ImageUri` is supported alongside ZIP Lambdas. cdkd reads the
+function's local `Dockerfile` from `cdk.out` and runs `docker build`
+locally before invoking. When no asset matches (typically: invoking a
+stack deployed elsewhere), cdkd falls back to `docker pull` from
+ECR — same-account / same-region only in v1; cross-account /
+cross-region is deferred to a follow-up PR. `Architectures: [x86_64]` /
+`[arm64]` are honored via `--platform` so an arm64 host running an
+x86_64 Lambda doesn't hit emulation.
+
 ```bash
 # Invoke by CDK display path (single-stack apps may omit the prefix)
 cdkd local invoke MyStack/MyApi/Handler
@@ -620,6 +632,39 @@ cdkd local invoke MyStack/Handler --from-state
 See [docs/cli-reference.md](docs/cli-reference.md#local-invoke-run-lambda-functions-locally)
 for the full surface, target-resolution rules, and v1 scope notes.
 
+## `local start-api`: long-running local API server
+
+`cdkd local start-api` stands up a long-running local HTTP server that
+maps the synthesized API Gateway routes (REST v1, HTTP API, Function
+URL) to local Lambda invocations against the same RIE-backed Docker
+containers `cdkd local invoke` uses. Modeled on `sam local start-api`
+but reusing cdkd's synthesis / route-discovery plumbing.
+
+```bash
+# Auto-allocate a port (printed at startup) and serve every discovered route
+cdkd local start-api
+
+# Pin to port 3000 (SAM-parity / curl muscle memory)
+cdkd local start-api --port 3000
+
+# Pre-warm one container per Lambda at server boot — eliminates first-request cold start
+cdkd local start-api --warm
+
+# Override env vars per-Lambda (SAM-shape file)
+cdkd local start-api --env-vars env.json
+
+# Pin the deployed execution role per Lambda (or globally with a bare ARN)
+cdkd local start-api --assume-role MyApiHandler=arn:aws:iam::123:role/handler-role
+```
+
+v1 scope (PR 8a): REST v1 + HTTP API + Function URL with AWS_PROXY
+integrations only. Authorizers, CORS preflight, hot reload, stage
+variables, and WebSocket APIs are deferred to follow-up PRs.
+
+See [docs/cli-reference.md](docs/cli-reference.md#local-start-api-long-running-local-api-server)
+for the full route-discovery rules, container-pool semantics, and exit
+codes.
+
 ## State Management
 
 State is stored in S3 with optimistic locking via S3 Conditional Writes