Expose credentials.NewRequestInfoContext as a public (experimental) API

[vadimsht]

Use case(s) - what problem will this feature solve?

We have a Go library that reuses gRPC code generator and many of APIs, but uses an alternative transport layer (simple HTTP request/responses): http://go.chromium.org/luci/grpc/prpc The can historically be traced to lack of HTTP2 support on Google Appengine and it solves the same problem as solved by grpc-web proxy, except without a proxy.

We are morphing this library to be closer and closer to the real gRPC client, to do a full switch at some point.

As part of that, it would be nice to be able to use PerRPCCredentials. Unfortunately, many implementations of this interface call credentials.RequestInfoFromContext(ctx) to check the security level etc. And this is impossible to setup without access to internal https://pkg.go.dev/google.golang.org/grpc/internal/credentials#NewRequestInfoContext

Proposed Solution

Please consider making this API public. This will also likely help with unit-testing PerRPCCredentials implementations.

[eshitachandwani]

Hey @vadimsht , thank you for your suggestion regarding making credentials.NewRequestInfoContext public.
This request requires careful consideration and discussion with other maintainers, as it involves exposing internal APIs. We need to assess the potential impact on security and future development. I will discuss it with other maintainers and get back to you !