Comparing a164c24e8e...d8f6981be1 - api - Gitea

groombook/api

Author	SHA1	Message	Date
Flea Flicker	d8f6981be1	revert(api): remove /health/ready — superseded by /api/readyz (GRO-2689) CI / Lint & Typecheck (pull_request) Successful in 18s Details CI / Test (pull_request) Successful in 25s Details CI / Build & Push Docker Images (pull_request) Successful in 53s Details CTO architectural ruling (PR #235 review): K8s readiness/liveness probes must remain DB-less to prevent transient DB blips from cycling pods. The /api/readyz endpoint (GRO-2687) is the canonical DB-health signal for the monitoring layer and satisfies the GRO-2678 detection-gap requirement. Removes: - GET /health/ready route from src/index.ts - src/__tests__/health-ready.test.ts Refs GRO-2689, GRO-2687, GRO-2678	2026-08-09 09:48:10 +00:00
Flea Flicker	d7bb314087	feat(api): add DB-touching /health/ready readiness probe (GRO-2678) CI / Lint & Typecheck (push) Successful in 19s Details CI / Test (push) Successful in 21s Details CI / Build & Push Docker Images (push) Successful in 34s Details CI / Build & Push Docker Images (pull_request) Successful in 23s Details CI / Lint & Typecheck (pull_request) Successful in 20s Details CI / Test (pull_request) Successful in 21s Details	2026-08-09 09:26:17 +00:00
Flea Flicker	7679fada0a	feat(api): add DB-touching /health/ready readiness probe (GRO-2678) CI / Lint & Typecheck (pull_request) Successful in 19s Details CI / Test (pull_request) Successful in 21s Details CI / Build & Push Docker Images (pull_request) Successful in 3m25s Details Register GET /health/ready before the /api/* auth middleware so it is public and reachable by K8s readinessProbe on port 3000 without auth. On success → 200 {"status":"ready"}; on any DB/schema failure → 503 {"status":"degraded"}. Logs the pg error code; never leaks SQL in body. A dropped schema (42P01) surfaces as non-200, closing the /health mask that allowed the GRO-2678 incident to go undetected for ~43h. Add health-ready.test.ts covering the 200 success path, 503 on schema drop (42P01), and 503 on connection error; all assert no SQL leakage. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-08-09 09:21:56 +00:00

Diff Content Not Available