-
Notifications
You must be signed in to change notification settings - Fork 845
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
Re-enable shorthand HTTP API #5168
Conversation
service/frontend/http_api_server.go
Outdated
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: I still see a couple of references to gogo in comments in this file.
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 have enough context to know whether the claims there are still true. @cretz, as the author, do the claims about gogo-status-compatible but not grpc-status-compatible in errorHandler still hold?
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 only had a couple of nits.
Not super familiar with this part of the codebase but the changes LGTM.
I also added tests for all four mime-types we support to ensure we _actually_ support each of them.
9bcdbdb
to
e16d1be
Compare
I'm setting this to automerge when tests pass to unblock other work that's hurt by the api-go changes. This should be the last time I break things |
What changed?
This re-enables the shorthand payload format for our HTTP API.
Why?
This is a business requirement for our HTTP API.
How did you test it?
I updated our HTTP API tests to test all four mimetypes we support
Potential risks
None
Is hotfix candidate?
No.