Configuring gRPC server with spring cloud config

[primoze]

Is there any way to configure the gRPC server with the spring cloud config client extension? My logs show that the server is being queried, and the config keys exist (quarkus.grpc.server.port), but the gRPC server tries to start on port 9000, which is unavailable. I tried adding my own ConfigSource implementation, and using that the gRPC server picks it up. Any reason the config server isn't being used, or is it a bug?

[quarkus-bot[bot]]

/cc @alesj (grpc), @aureamunoz (spring), @cescoffier (grpc), @edeandrea (spring), @geoand (spring), @radcortez (config)

[primoze]

Yes, that applies the fetched config correctly; in this case applying only the main one merged with euc1, ignoring aws, as above (which isn't technically the case; see below).

I missed this the other day: the app actually does fetch all the configs from the server, but does so in three separate batches:

Adding property source: Config resource 'file [/<path>/app.yml]' via location 'file:/<path>/'

Adding property source: Config resource 'file [/<path>/app-aws.yml]' via location 'file:/<path>/'
Adding property source: Config resource 'file [/<path>/app.yml]' via location 'file:/<path>/'

Adding property source: Config resource 'file [/<path>/app-euc1.yml]' via location 'file:/<path>/'
Adding property source: Config resource 'file [/<path>/app.yml]' via location 'file:/<path>/'

So the last profile wins. But the original library fetches them in two:

Adding property source: Config resource 'file [/<path>/app.yml]' via location 'file:/<path>/'

Adding property source: Config resource 'file [/<path>/app-euc1.yml]' via location 'file:/<path>/'
Adding property source: Config resource 'file [/<path>/app-aws.yml]' via location 'file:/<path>/'
Adding property source: Config resource 'file [/<path>/app.yml]' via location 'file:/<path>/'

For reference, here are the urls requested by the test springboot app:

• http://localhost:8888/app/default for the first request
• http://localhost:8888/app/prod,aws,euc1 for the second

While quarkus makes these requests:

• http://localhost:8888/app/prod
• http://localhost:8888/app/aws
• http://localhost:8888/app/euc1

The profiles should all be fetched in a single request, and the default profile request is missing.

[radcortez]

I'll need to have a look.

By any chance, do you have a Spring Boot app that I can use to test?

[primoze]

Yeah, I used the below:

Here's the app: quarkus-51856-scc-app
And the config repo: quarkus-51856-scc-config
And the config server: quarkus-51856-scc-server

Once the scc-app is running you can curl it curl localhost:8090/value
and get {"grpc":"6568","http":"8083"}, or you can change it to log on startup.

The server logs request url and headers.

[radcortez]

#52435 should fix the behaviour difference. Can you give it a try?

Sorry for the delay. And thank you so much for the reproducers. They really helped.

[primoze]

Tried on the latest snapshot, seems to work fine, except the first default request is missing. I think that's OK for our use case, but might not be for all. I think spring uses it to enable additional profiles, which are then fetched in the second request.

Looks like it works both with QUARKUS_PROFILE and QUARKUS_SPRING_CLOUD_CONFIG_PROFILES.

Thanks for the fix!