Discovery-based Configuration Server Integration for Spring Cloud Config in Quarkus

[poldinik]

Description

Currently, the Quarkus extension for Spring Cloud Config Server supports configuration via a fixed URL using the property:

quarkus.spring-cloud-config.url=http://localhost:8888

This proposal aims to enhance this integration by introducing support for service discovery-based configuration using a system such as Eureka. By allowing configuration through properties like:

quarkus.spring-cloud-config.discovery.enabled=true
quarkus.spring-cloud-config.discovery.serviceId=config-server-id

Quarkus applications would be able to dynamically locate the Spring Cloud Config Server through a service registry, removing the need to hardcode server URLs. This is especially useful in environments heavily integrated with the Spring Cloud and Netflix OSS ecosystems, where service discovery is a core architectural component.

The implementation would leverage the existing community effort around Eureka integration in Quarkus, such as the project at https://github.com/fmcejudo/quarkus-eureka, potentially evolving it into a supported extension or using it as a reference.

Implementation ideas

No response

[quarkus-bot]

/cc @aureamunoz (spring), @geoand (spring), @radcortez (config)

[geoand]

Sounds interesting. Is this something you would be interested on working on @poldinik ?

[poldinik]

@geoand Yes, I will work and open a PR with a solution

[poldinik]

Hi, I have opened a draft of solution

#48121

The proposed solution is a lazy provider of url. The configuration can be done with

quarkus.spring-cloud-config.discovery.enabled=true
quarkus.spring-cloud-config.discovery.serviceId=config-server-id
quarkus.spring-cloud-config.discovery.eureka-service-url.defaultZone=http://localhost:8761/eureka/