https://buf.build/blog/buf-curl/
Didn't dig deeper to see if the bud tooling can help me deciding protobufs laying around when it's not about a grpc call
(If you want a "registry," the better approach would be to have something that uses all the services as dependencies to consolidate their protos.)
2) Going along with this approach, gRPC has a reflection service; most server implementations can expose this (I have personally done it with Tonic/Rust but I know Golang and Java bindings, probably Ruby and others, support it). If you use something like gRPCurl against a server with reflection, the only "path flags" you have to worry about are, like... just the method names. It can't really get more terse than it is with gRPCurl and gRPC reflection, though autocomplete would be nice to have I guess.
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?