-
Notifications
You must be signed in to change notification settings - Fork 40
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
[storage][front-end] Add google.api.http #186
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.
other than the url paths/names, looks good.
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.
url paths and names need to change
See https://grpc-ecosystem.github.io/grpc-gateway/docs/tutorials/adding_annotations/#using-protoc Signed-off-by: Boris Glimcher <Boris.Glimcher@emc.com>
Following Google AIP-127 - HTTP and gRPC Transcoding Related to opiproject#174 Signed-off-by: Boris Glimcher <Boris.Glimcher@emc.com>
Signed-off-by: Boris Glimcher <Boris.Glimcher@emc.com>
fixed |
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'm not positive that this is correct because I've never implemented protobuf over REST/http. I'd say that if the proto compiler works, it's probably fine to merge. I'd also add a backlog item for building out (at least a mock) http server to see if it works as expected.
opened #188 to track backlog item |
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.
one comment @glimchb on the path hierarchy
Shouldn't the objects "hierarchy" be part of the the URLs (like in this example)? |
Yes, it should. I just didn't want to overload this PR with hierarchy since it can lead to a heavy discussion on who is parent of who... I opened #188 to track the correct hierarchy fixes |
} | ||
rpc NVMeSubsystemUpdate (NVMeSubsystemUpdateRequest) returns (NVMeSubsystem) { | ||
option (google.api.http) = { | ||
patch: "/v1/subsystems" |
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 shoud have been:
patch: "/v1/subsystems/{subsystem}"
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.
Thanks, good catch!
@glimchb late response. looks good. |
Following Google AIP-127 - HTTP and gRPC Transcoding
and https://cloud.google.com/endpoints/docs/grpc/transcoding
Related to #174
Signed-off-by: Boris Glimcher Boris.Glimcher@emc.com