Configuring clients of a config server
To be able to get their configurations from the config server, our microservices need to be updated. The microservices will use Spring’s retry mechanism to reconnect to a config server. This is especially useful when the whole landscape of microservices and its config server are started simultaneously – for example, when using the docker compose up command.
In this scenario, many of the clients will be trying to connect to the config server before it is ready, and the retry logic will make the clients connect to the config server successfully once it is up and running.
Initially, Spring Cloud Config provided a bootstrap mechanism for clients to connect to the server. Starting with Spring Boot 2.4, configuration data can be imported using the spring.config.import property. This has become the default approach for connecting to Spring Cloud Config Server.
However, in scenarios where we need to define multiple...
