Closed kjthorpe18 closed 10 months ago
Is it possible that you have an environment variable (e.g. from kubernetes) that is GRPC_CLIENT_CERT
?
Also maybe you don't want to ship the client lib, if you don't plan to use it.
Ah I think it does have that variable. It has a shared environment variable file with other applications, and has GRPC_CLIENT_CERT
, GRPC_SERVER_CERT
, etc. defined with a file path like export GRPC_CLIENT_CERT="file:/opt/grpc/cert/grpc_client_cert.crt"
. But, still not sure why this would be picked up the way it is in the error?
And yeah, I have the client auto configs it excluded from the main application context now, but need them for integration tests, so I'm including them there.
I think I have two issues here:
GRPC_CLIENT_CERT
, when it should be a different one for grpc.server.security.trust-cert-collection
.GRPC_CLIENT_CERT
set in the environment, this error is thrown. Something is picking up that environment variable and trying to use it
The context
Moving to version
2.15
from2.14
to support an application on Spring Boot 3.1 with autoconfiguration. This application is a gRPC server, NOT a client.EDIT: added env vars and their use in the application properties. Environment variables set:
The bug
The application fails to start, possibly because
grpc.client.*
application properties are not defined, but this is not a grpc client. I do not have client properties set. Possibly this is due to the 2.15 auto configuration changes?Stacktrace and logs
The application's environment
Which versions do you use?