-
Notifications
You must be signed in to change notification settings - Fork 65
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
Safely providing logging output from failed hub health checks #585
Comments
This would be great help. The problem is that |
Ah yes, thank you. Updating top comment. |
Can you remind me what the undesired output looks like? Is it just the options defined in
|
Or better yet, if there's a way I can locally force a failed test without actually deploying anything - that would be grand 😁 |
If my above assumption is correct, I think "all" we have to do is add |
See minimal working example here https://gist.github.com/sgibson91/5b31ee1b18832ae785565da99fe605a2 |
I think it is a good enough compromise... |
Summary
At the moment, our hub health checks in
deployer
only output pass or fail, without any indication to what caused the failure. This is because when pytest fails like this, it exposes any secrets on the command line. At the minute to diagnose the failure, we have to get the logs directly from the hub pod. Which is fine, but if you don't already have access to the clusters setup, it can be disruptive to flow.We should think about safe ways for the deployer to provide feedback when a hub health check fails.
The text was updated successfully, but these errors were encountered: