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.
I discovered this useful introspection technique trying to use grpcurl
https://github.com/fullstorydev/grpcurl
I know one of the use cases of the HTTP API is because they are easy to
use and more familiar.
I think we just need to write and share a bit more about how to use the
gRPC server. The gRPC community is pretty big and their tools can help
with that.
More about reflection https://github.com/grpc/grpc-go/blob/master/Documentation/server-reflection-tutorial.md
In practice
With this PR merged I am able to inspect the grpc server using grpcurl:
And I can list hardware for example:
Still have to figure out how to push values, grpcurl support a
-d
field as curl but i didn't have it working yetSigned-off-by: Gianluca Arbezzano gianarb92@gmail.com