by vlowrian on 2/20/23, 8:18 AM with 15 comments
by kevincox on 2/20/23, 5:26 PM
The introspection could be a little slow if the server was far away (it added a couple round trips) but the ability to avoid knowing where the schemas were was invaluable. (I wonder if there could have also been some sort of caching to make it a bit better).
by codetrotter on 2/20/23, 11:37 AM
gRPCurl, Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
https://github.com/fullstorydev/grpcurl
The readme in your link mentions how they are different:
> How is protocurl different from grpccurl? grpccurl only works with gRPC services with corresponding endpoints. However, classic REST HTTP endpoints with binary Protobuf payloads are only possible with protocurl.
For my purposes, gRPCurl was a good fit. Maybe to others as well.
by RutZap on 2/20/23, 3:58 PM
by ithkuil on 2/20/23, 11:38 AM
For example, I miss an easy way to stuff all my (and my team's) protobufs in a registry and a tool that autodetects what schema a protobuf is (or leverages the type in Any), so that I can avoid passing complicated path flags to all these tools that decode protos.
Any ideas?
by fisian on 2/20/23, 3:15 PM
Unfortunately, those options are poorly documented, so it took me some time to figure that out.
by 2h on 2/20/23, 3:07 PM
by cjbprime on 2/20/23, 5:11 PM