-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding healthcheck command to docker #173
Conversation
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
var hostSettings = new HostSettings( | ||
configuration.ReturnQueue, | ||
$"Queue creator for {configuration.ReturnQueue}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
without looking at the signature... should this be a different description?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this matters
return (false, e.Message); | ||
} | ||
|
||
return (true, string.Empty); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so if it fails for any reason other than brokerunreachable it will still be marked as healthy? This is the description of the healthchecker... but seems to me like it could cause some confusion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so if it fails for any reason other than brokerunreachable it will still be marked as healthy?
no, it will be an unhandled exception and therefore it will be exit code 1
This adds a new
health-check
command to the CLI, and then we use it to check if the container is healthy.