litellm/tests/test_litellm/proxy/health_endpoints
yuneng-jiang be37cf782c fix(proxy): expose db status on public /health/readiness
Backport of #27866 onto litellm_1.84.0rc2.

External readiness probes consumed the legacy detailed payload's `db`
field to drive alerting and pod-rotation decisions. Stripping the body
to {"status": "healthy"} broke those probes silently — the HTTP code
still flipped to 503, but probes checking body.db == "connected"
treated the response as healthy.

Add `db` back to the unauthenticated payload. The rest of the diagnostic
fields (litellm_version, callbacks, cache, log_level) stay behind
/health/readiness/details so the recon-leak gate from #26912 holds.
Values match the legacy contract: "connected", "disconnected",
"Not connected". The 503-on-DB-disconnect behavior from LIT-2607 is
preserved.
2026-05-13 13:18:54 -07:00
..
test_health_endpoints.py fix(proxy): expose db status on public /health/readiness 2026-05-13 13:18:54 -07:00