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.
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
feat(manifest): add HTTP Health Check hidden fields #1592
feat(manifest): add HTTP Health Check hidden fields #1592
Changes from 10 commits
b09f875
3647310
f72c8ba
2af5287
9017edf
945c67c
dba23a2
fa2bfeb
3876af8
ebcdb9c
6f0d31c
ccb5a5a
89969dd
da4df77
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
nit: let's remove words like cannot from the error message unless it's in the
cli
pkg (the root pkg)https://github.com/uber-go/guide/blob/master/style.md#error-wrapping
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 think it is fine to keep
can't
in this scenario since it is already the root error instead of wrapping the other error. Agree if we are wrapping error we want to avoid piling up likefailed to get health check: can't unmarshal health check
. And instead we wantget health check: can't unmarshal health check
. What do you all think?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.
More the opposite,
cannot get health check: unmarshal health check
. Where the root error that wraps others can use "cannot" to make it more human friendly but "library" pkgs shouldn't put cannot in their error messagesThere 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.
But according to https://github.com/uber-go/guide/blob/master/style.md#error-wrapping, isn't
cannot get health check: unmarshal health check
a bad example?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.
Ah I wish we could change this :'( but we would need to support both
targetContainer
andtarget_container
to maintain backwards compatibility.Right now this will break users that have
targetContainer
as a field. We'd need to figure out a way of assigning two yaml fields toTargetContainer
.Maybe this works?
If it does great, otherwise can we punt this change to a separate PR?
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.
Okay, so that ☝️ didn't work and some digging/reading makes me think there isn't a built-in way to do this, but this little hack works:
In
manifest/lb_web_svc.go
, I added another field to the struct for camel case.In
stack/lb_web_svc.go
: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.
brilliant! that sounds good to me!
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.
samesies thanks for diving deep on this!