[marcoacierno]

• Build the Resonate client in one expression
• Run Resonate and its worker on the ECS cluster

What

ToDo

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
pycon	Ready	Preview	Oct 30, 2026 8:00pm UTC

[claude]

Adds a Resonate server (ECS service backed by a resonate Postgres database on the existing RDS instance) and a resonate_worker service running the backend's manage.py resonate_worker, plus a security-group opening for port 8001 and a RESONATE_URL env var shared by all backend tasks.

• Swapped names in cluster/security.tf: in_resonate is an egress rule and out_resonate is an ingress rule, and the comment on out_resonate is attached to the wrong one. Both are needed, but the names and comment should match their types.
• Plaintext DB credentials in the task definition: resonate/task.tf puts the full postgres://user:password@... URL in the container environment, so it shows up in the task definition and the console. Use secrets (SSM/Secrets Manager) if the other services do, or at least mark the value sensitive.
• Database must exist beforehand: the resonate DB is not created anywhere. The service will crash-loop on first apply, and deployment_minimum_healthy_percent = 0 makes that visible only as downtime. Document the step or automate it.
• Placeholder healthcheck on the worker: echo 1 always succeeds, so ECS never detects a dead worker. Check the worker process instead, or drop the healthCheck.
• Resonate server has no auth and the image tag is pinned by version only: the server listens on 0.0.0.0:8001 with no auth, and the SG rule allows any member of the server SG to reach it. That is acceptable only if nothing public shares that SG. Check this.
• Minor: systemControls with somaxconn and the fixed memoryReservation = 10 on non-prod were copied from the web task. The worker doesn't need the first, and 10 MB is unrealistically low for a Python process that holds an open connection.
• Comment style: several new comments in the PR explain rationale at 3–4 lines. Trim them to the one or two lines the repo guidelines call for.

No tests are included, which is expected for Terraform-only changes.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 92.47%. Comparing base (bd31258) to head (1765b37).

Additional details and impacted files

@@             Coverage Diff              @@
##           resonate    #4824      +/-   ##
============================================
+ Coverage     92.43%   92.47%   +0.04%     
============================================
  Files           358      358              
  Lines         11272    11267       -5     
  Branches        911      909       -2     
============================================
  Hits          10419    10419              
+ Misses          742      737       -5     
  Partials        111      111              

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.