Conversation
…tion Align admin topics endpoints with admin-role enforcement, standardize measure_system usage, and normalize/validate model codes against MODEL_REGISTRY so configuration is consistent across routes and persisted topics. Sync the admin specification with the implemented request/response contracts and status behavior. Co-authored-by: Cursor <cursoragent@cursor.com>
fix(#236): align admin topics auth, type naming, and model codes
Map legacy test-era model identifiers to canonical MODEL_REGISTRY codes and guard model-code normalization against non-string mocked values so seeding and AI-engine unit paths remain stable under strict model validation. Co-authored-by: Cursor <cursoragent@cursor.com>
fix(#236): restore legacy model-code compatibility for CI tests
Use stage-aware template metadata and secret lookups so prod/staging/dev resolve the correct AWS resources, and replace deprecated utcnow usage in Pulumi build timestamp generation. Co-authored-by: Cursor <cursoragent@cursor.com>
Use a context-relative Dockerfile path so docker builds succeed consistently in Pulumi updates across environments. Co-authored-by: Cursor <cursoragent@cursor.com>
…provider Set the Dockerfile path to the provider-resolved location so preview and update can read the file during image builds. Co-authored-by: Cursor <cursoragent@cursor.com>
Use resolved absolute context and Dockerfile paths to avoid Windows path resolution failures during Docker image builds in Pulumi. Co-authored-by: Cursor <cursoragent@cursor.com>
Update CORS origin regex to allow both purposepath.app and subdomains so OPTIONS preflight for execute-async no longer returns 400 from the app middleware. Co-authored-by: Cursor <cursoragent@cursor.com>
|
🍹 The Update for mottych/purposepath-coaching-api/dev (at e5d54d9) was successful. ✨ Neo ExplanationA code change triggered a Docker image rebuild for the coaching API, which updates the Lambda function to run the new container version—a standard, low-risk code deployment.Root Cause AnalysisThis deployment was triggered by a code change in the repository. The coaching API application code was modified, causing Docker to rebuild the container image with a new timestamp (2026-02-15T22:07:21). This is a standard code deployment cycle where application logic, dependencies, or configuration within the Docker image has been updated. Dependency Chain
Risk AnalysisRisk Level: Low No stateful resources are being modified. This is a routine application deployment updating Lambda function code via a new container image. The Lambda function itself is not being replaced—only its image reference is being updated. No database, storage, or networking changes are involved. Zero risk of data loss or downtime (Lambda handles blue-green deployments automatically). Resource Changes Name Type Operation
~ coaching-image docker:index/image:Image update
~ coaching-api aws:lambda/function:Function update
|
Include the pending admin health route file changes on dev to keep branch state aligned before promotion. Co-authored-by: Cursor <cursoragent@cursor.com>
AWS Lambda rejects updates when AWS_REGION is set explicitly in function environment variables. Remove it and rely on the runtime-provided region variable. Co-authored-by: Cursor <cursoragent@cursor.com>
Format files flagged by Ruff format check in CI to unblock dev->staging promotion checks. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
devtostaging, including stage-aware secret/table resolution needed for environment-specific runtime resources.Test plan
pulumi preview --stack prod --target coaching-apishows expected Lambda env-var additions.pulumi up --stack dev(currently blocked in this environment by Dockerfile path resolution during Pulumi Docker image build; details in PR notes).