🔧 feat: enhance readiness endpoint with detailed connection status
- Upgraded readiness endpoint to provide per-connection health status
- Added structured JSON response with connection details
- Database health status now includes explicit healthy/unhealthy/not_configured states
- Better observability with detailed failure reasons
- Maintains backward compatibility with existing readiness checks
Response Examples:
✅ Healthy: {ready: true, connections: {database: {status: healthy}}}
❌ Unhealthy: {ready: false, reason: database_unhealthy, connections: {database: {status: unhealthy, error: ...}}}
❌ Shutting Down: {ready: false, reason: server_shutting_down, connections: {database: not_checked}}}
Benefits:
- Detailed health information for debugging
- Per-connection status (database, future: cache, etc.)
- Better Kubernetes/container orchestration integration
- Clear failure reasons for troubleshooting
- Extensible for additional services
Testing:
- ✅ Readiness endpoint returns detailed connection status
- ✅ Database health properly reflected
- ✅ All 25 BDD scenarios passing
- ✅ All unit tests passing
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
Gabriel Radureau
107bae528a