Ever found yourself SSH’d into multiple servers just to tweak a database URL or an API key for your microservices? It’s a common headache: managing configuration that’s duplicated, out-of-sync, and a nightmare to update across your distributed system. This manual approach not only wastes valuable developer time but also introduces significant risk of configuration drift and deployment errors. What if you could have a single source of truth for all your Spring Boot application’s settings, managed in a version-controlled repository, and dynamically reloaded by your services?
Spring Cloud Config Server provides exactly this solution. It acts as a central hub for externalized configuration, allowing your microservices to fetch their settings at runtime. Typically, this server integrates with a Git repository, making your configuration transparent, auditable, and easily manageable through familiar Git workflows. This means you can update a property in Git, commit, and push, and then have your services pick up the changes without requiring a restart, thanks to Spring Cloud’s refresh mechanisms.
To get started, you’ll need to set up a Spring Cloud Config Server project. This involves adding the spring-cloud-config-server dependency and configuring it to point to your Git repository. You’ll also need a client application (your microservice) to consume this configuration. The client application requires the spring-cloud-starter-config dependency and a bootstrap configuration file (or a bootstrap.yml/bootstrap.properties file in Spring Boot 2.x and earlier) to specify the URI of the Config Server.
Here’s a minimal example of how you might configure your Config Server to fetch properties from a Git repository. Assume your Git repository has a file named application.yml at its root.
spring:
application:
name: config-server
cloud:
config:
server:
git:
uri: file:///path/to/your/local/git/repo/config-repo
default-label: main
Try it: Create a new Spring Boot project, add the spring-cloud-config-server dependency, and configure it to point to a local directory containing a simple application.yml file. Run the server and then set up a separate Spring Boot client application with spring-cloud-starter-config to fetch a property from it.