Repository navigation
expose readiness failures when application metadata is unavailable - #69
Conversation
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
@jules Please review and address the following items for this PR: Issues to Fix
How to Confirm the FixRun the following commands to confirm everything passes: pytest tests/backend/test_health_check_status.py -v
python3 scripts/generate_requirements.py
pytest tests/backend/test_requirements_sync.py |
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
… postgres configured
Exposes application readiness health endpoints (/ready, /readiness, /health/ready, /healthz/ready) that verify required relational schema and metadata access across both SQLAlchemy engine and direct database pathways. Keeps cheap liveness probes on /health and /healthz, sanitizes public diagnostic responses, and documents readiness dependencies.
Fixes #50
PR created automatically by Jules for task 13982862318872597189 started by @spelech