We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
when i use grpc-gateway to proxy the storage gRPC service, i found the same http route in the .gw.pb files.
for example: storage/v1alpha1/frontend_nvme_pcie.proto
rpc ListNvmeSubsystems (ListNvmeSubsystemsRequest) returns (ListNvmeSubsystemsResponse) { option (google.api.http) = { get: "/v1/{parent=subsystems}" }; option (google.api.method_signature) = "parent"; }
and
rpc ListNvmeControllers (ListNvmeControllersRequest) returns (ListNvmeControllersResponse) { option (google.api.http) = { get: "/v1/{parent=subsystems}" }; option (google.api.method_signature) = "parent"; }
above two different rpc method: ListNvmeSubsystems、ListNvmeControllers has the same http anotation url.
The text was updated successfully, but these errors were encountered:
Duplicates/relates to #188 ?
Sorry, something went wrong.
not the same, but the issue #188 can also resolve the problem after redefine the rpc methods http anotations according to business rules.
@chujieyang some was fixed by #317 can you propose a fix for the rest, please ?
I hava submit a pull request with the http anotations. #331
thanks!
Successfully merging a pull request may close this issue.
when i use grpc-gateway to proxy the storage gRPC service, i found the same http route in the .gw.pb files.
for example: storage/v1alpha1/frontend_nvme_pcie.proto
and
above two different rpc method: ListNvmeSubsystems、ListNvmeControllers has the same http anotation url.
The text was updated successfully, but these errors were encountered: