Mastering Spring Cloud

Monitoring repository changes on a Config Server

Spring Cloud Config Server has to perform two tasks in the previously described process. First of all, it has to detect changes in a property file stored in a Git repository. This may be achieved by exposing a special endpoint, which would be called through a WebHook by the repository provider. The second step is to prepare and send a RefreshRemoteApplicationEvent targeted at the applications that might have been changed.  This in turn requires us to establish connection with a message broker. The spring-cloud-config-monitor library is responsible for enabling the /monitor endpoint. To enable support for the RabbitMQ broker, we should include the same starter artifact as for the client application: ...