-
|
I have a Quarkus service that has a gRPC client. The Quarkus application does not set the host/port of the gRPC client in the application.yml/properties, as this needs to be set at deployment. So I spin up a container that hosts this Quarkus app, where I set the following environment variables on the container: But I still get this during startup:
Am I misunderstanding something about how to configure the gRPC client? Why are these environment variables not working? When testing the application I am putting in the container, if I run it locally in test mode with the following application-dev.yml configuration, it does work: All my other environment variables are picked up fine by Quarkus |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
/cc @alesj (grpc), @cescoffier (grpc), @edeandrea (container-image), @geoand (container-image), @radcortez (config) |
Beta Was this translation helpful? Give feedback.
-
|
I have tested both |
Beta Was this translation helpful? Give feedback.
Do you have a dotted named property in your deployed application? Setting only
QUARKUS_GRPC_CLIENTS__RUNTIME_REPORTER__HOSTis not enough, because we dont know how to matchRUNTIME_REPORTER. Is itruntime.reporterorruntime-reporter? By default, it uses the dot.So in these cases, you need to add a
quarkus.grpc.clients.runtime-reporter.hostsomewhere (it may be empty) to help disambiguate the name. Please check https://quarkus.io/guides/config-reference#environment-variables