What's the credentials, grpc and reflection packages? Where are they coming from.

grpc is from "google.golang.org/grpc"
credentials is from "google.golang.org/grpc/credentials"
reflection is just for grpc build in service discovery "google.golang.org/grpc/reflection"

https://github.com/grpc/grpc-go/tree/master/examples

I am not clear what is the issue about. Do you want an example to be added for the GetCertificate method ?

https://godoc.org/golang.org/x/crypto/acme/autocert#Manager.GetCertificate requires a hello *tls.ClientHelloInfo I have no idea how I should provide one, sorry

Once I know how to make a hello *tls.ClientHelloInfo manually, the rest should be ok

I don't have much experience about the package, but from the documentation it seems this function serves as a hook for tls.Config.

s := &http.Server{
    Addr:      ":https",
    TLSConfig: &tls.Config{GetCertificate: m.GetCertificate},
}

Exactly and this makes it complicated for me because a grpc server needs the certificates directly. A grpc server has no TLSConfig hook as the build in https golang server does. I need the return value form the function GetCertificate itself to pass to credentials.NewServerTLSFromCert

Is there a bug against grpc about this too? It might be best handled by them.

Even if we were to documented some convoluted workaround to make the pieces all fit together, not everybody will read the docs and want to jump through those hoops.

It might be best if grpc made some API changes on their side to make this easy.

Use NewTLS instead of NewServerTLSFromCert.

https://godoc.org/google.golang.org/grpc/credentials#NewTLS

We can't add examples for how to plug a tls.Config into all possible client libraries, but let us know if you have an idea of how we could have made that more clear.

Thank you, feel free to paste answer in stackoverflow