[codex] Add container health check endpoint#754
Draft
dorakingx wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/healthzendpoint for container liveness checks/healthzWhy
Issue #474 asks for a health-check endpoint for container orchestration. The existing
/healthresponse is more descriptive, while/healthzgives orchestrators a minimal stable target that only needs to return 200 and{ "status": "ok" }.Validation
git diff --check/health,/healthz, and/pingdocker-compose.ymland verified the backend healthcheck points at/healthzNote: running the repo's pytest command locally is blocked by missing native
libmagicon this machine (ImportError: failed to find libmagic). The endpoint was still validated with TestClient using a local import stub for the unrelatedmagicdependency.Closes #474