[Chore-1129] Persist app API Lambda memory

Story 1129Epic None1 files · +1/−1

PR #286 · pramaan-io/pramaan-functions · merged 2026-06-09

Why this matters

Cold-start tuning can silently revert to 256 MB on the next deploy.

Why app API Lambda needs the memory setting baked into the deploy itself.

Manual console settings do not survive the next deploy.

The fix — Write Lambda memory in the deploy file, not the console — so cold-starts stay fast forever.

How it flows

sequenceDiagram
  autonumber
  participant dev as Developer
  participant git as GitHub Actions
  participant aws as AWS Lambda
  dev->>git: commit memory: 1024 to deploy-app-api.yml
  git->>git: read 1024 MB from workflow
  git->>aws: deploy with --memory-size 1024
  aws->>aws: Lambda boots with 1024 MB — fast cold start

Files changed (1)

File±
.github/workflows/deploy-app-api.yml ★+1 −1