Run the ERA5 lake service in every environment #20

Merged

admin_emi merged 1 commit from feat/lake-all-envs into dev

2026-07-23 22:32:15 +00:00

admin_emi commented

2026-07-23 22:31:10 +00:00

Owner

Lake service in the compose stack (beta + LAN) with creds via vault (beta) / Actions secrets (LAN); deploy scripts roll it with backend; compose configs validated for base and dev overlay.

admin_emi added 1 commit 2026-07-23 22:31:12 +00:00

Run the ERA5 lake service in every environment

PR build (required check) / changes (pull_request) Successful in 9s

Details

secrets-guard / encrypted (pull_request) Successful in 8s

Details

PR build (required check) / build-frontend (pull_request) Has been skipped

Details

PR build (required check) / build-backend (pull_request) Has been skipped

Details

PR build (required check) / validate-observability (pull_request) Has been skipped

Details

PR build (required check) / gate (pull_request) Successful in 2s

Details

82e68e89f0

The lake was prod-stack-only; beta and LAN fell straight to NASA. Now the
compose stack gets the same service (backend image, THERMOGRAPH_ROLE=lake,
never host-published) and the backend points at it via THERMOGRAPH_LAKE_URL:

- deploy.sh rolls lake with every backend deploy (same image, different
  role); deploy-stack.sh's backend leg updates it too, tolerating stacks
  that predate the service.
- Creds: beta via the vault (added to beta.yaml); LAN via the Actions S3
  secrets injected by backend-deploy-dev.yml (dev renders no vault). Without
  creds the service stays healthy and answers 503 — reads fall through to
  NASA, so a credential gap can never take a page down.
- Dev overlay lifts the CPU caps like every other service.