Add optional health check endpoint#88
Open
mschout wants to merge 1 commit into
Open
Conversation
Enable a non-proxied health check via the HEALTHCHECK_PATH env var. Returns 200 when a valid CodeArtifact token is held, 503 otherwise.
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
1 participant
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.
Hi.
We are using this container in an AWS EKS cluster, and without the ability to register a "healthcheck" probe, the ELB wont see the container as healthy. I've added an optional heathcheck here, where if
HEALTHCHECK_PATHis set in the environment, then that specific path will respond with a 200 Ok response if the container appears healthy. I've just done a basic heuristic here checking if the token was refreshed recently to determine if its healthy or not.Open to suggestions to improve this, but this made it usable behind a loadbalancer that requires a healthcheck (e.g. ELB).