In the previous article, Introduction to Spring Cloud Config Server, we have seen how to use Spring Cloud Config Server.
But the problem is that to reload the config changes in Config Client applications, we need to trigger the /refresh endpoint manually. This is not practical or viable if you have a large number of applications.

Test

Spring Cloud Bus solves the problem of manually triggering /refresh on each Config Client when configuration changes. By adding the spring-cloud-starter-bus-amqp dependency and connecting services to a RabbitMQ message broker (run via Docker Compose), a single POST to /bus/refresh on any one service broadcasts the config update to all subscribed services automatically. The tutorial walks through setting up RabbitMQ, configuring two Spring Boot services (catalog-service and order-service) with Cloud Bus AMQP, and demonstrating how a single refresh endpoint call propagates changes across all instances.

Spring Cloud Tutorials – Auto Refresh Config Changes using Spring Cloud Bus