Skip to main content

Distributed configuration using spring cloud config

What is spring cloud config

Spring cloud config helps application in externalising the configuration properties in a server/client model. Which means there is a config server where all client application connects and read the properties related to their application. Properties can be accessed basis on application name and configured profile.
It supports resource based configuration using GIT repository or local file system over HTTP. Properties are managed in form of key-value pair. Though it easily integrate with spring boot application but can be used by any application in other languages also as properties can be accessed through REST URLs also.

We are going to learn below things here.

  1. GIT repository for configuration management
  2. Cloud config server
  3. Config client

GIT Repository

Here we are going to use GIT for configuration management which will be configured in config server. Setting up a GIT repository is very easy. We have to create the properties file using some naming pattern like <application_name>-<profile>.properties. Below is the structure of a GIT repository used for same purpose.


In above example "Config_repository" is our repository for configuration files where "microservice-app" is the application name and "DEV" or "PROD" is the profile name which details client application need to configure during connection to config server.
Below is the content of DEV properties file. Similarly PROD properties file will have details for production environment.
message=Welcome to Development!
world=Dev world

Cloud config server

We will create the config server using spring boot application. Below are the steps.

a. Create spring boot application
    You can either use spring initialiser ( or your favourite IDE to create the application.
b. Maven Dependencies
    Include below dependencies in your pom.xml.
c. Java configuration
    Below is the spring boot main class with required configuration annotation @EnableConfigServer.
public class CloudConfigApplication {

    public static void main(String[] args) {, args);
d. Cloud application configuration (application.yml)
    I have used YML for application configuration but properties file also can be used. Below is the content of configuration file. Here I have configured my git project for demonstration purpose.
server.port : 8888
          uri :
          username: ${git_user}
          password: ${git_password}
          force-pull: true config_user Lwre15qlw@
User name and password configured here will be required by config client to connect with it.

After starting the cloud config server, you can verify the URL in browser as given below.
Syntax: http://<host:port>/<application_name>/<profile>
Example: http://localhost:8888/microservice-app/DEV

It will show you the similar result as given below.
{"name":"microservice-app","profiles":["DEV"],"label":null,"version":"2e7c382ac0bcd2c35892960487451b333847c844","state":null,"propertySources":[{"name":"","source":{"message":"Welcome to Development!","world":"Dev world"}}]}

Cloud config client

Our config client application is created using spring boot application.

a. Create spring boot application
    You can either use spring initialiser ( or your favourite IDE to create the application.
b. Maven Dependencies
    Include below dependencies in your pom.xml.
c. bootstrap.yml
    A bootstrap configuration required to connect with cloud config server.
    active: PROD
      name: microservice-app
      uri: https://localhost:8888/
      username: config_user
      password: Lwre15qlw@
d. Properties usage
    Now our configuration is complete and we can use the properties in any of the spring managed class in the same way we do it in any regular spring application. See below example.
    private String message;
This concludes all the required components of spring cloud config server and client using GIT. Please let me know if you have any comment or suggestions.

If you are interested to know more about cloud configuration, like spring cloud bus using webhooks then please visit my another post.
config management using spring cloud bus


Post a Comment

Popular Posts

Setting up kerberos in Mac OS X

Kerberos in MAC OS X Kerberos authentication allows the computers in same domain network to authenticate certain services with prompting the user for credentials. MAC OS X comes with Heimdal Kerberos which is an alternate implementation of the kerberos and uses LDAP as identity management database. Here we are going to learn how to setup a kerberos on MAC OS X which we will configure latter in our application. Installing Kerberos In MAC we can use Homebrew for installing any software package. Homebrew makes it very easy to install the kerberos by just executing a simple command as given below. brew install krb5 Once installation is complete, we need to set the below export commands in user's profile which will make the kerberos utility commands and compiler available to execute from anywhere. Open user's bash profile: vi ~/.bash_profile Add below lines: export PATH=/usr/local/opt/krb5/bin:$PATH export PATH=/usr/local/opt/krb5/sbin:$PATH export LDFLAGS=&

Multiple data source with Spring boot, batch and cloud task

Here we will see how we can configure different datasource for application and batch. By default, Spring batch stores the job details and execution details in database. If separate data source is not configured for spring batch then it will use the available data source in your application if configured and create batch related tables there. Which may be the unwanted burden on application database and we would like to configure separate database for spring batch. To overcome this situation we will configure the different datasource for spring batch using in-memory database, since we don't want to store batch job details permanently. Other thing is the configuration of  spring cloud task in case of multiple datasource and it must point to the same data source which is pointed by spring batch. In below sections, we will se how to configure application, batch and cloud task related data sources. Application Data Source Define the data source in application properties or yml con

SpringBoot - @ConditionalOnProperty example for conditional bean initialization

@ConditionalOnProperty annotation is used to check if specified property available in the environment or it matches some specific value so it can control the execution of some part of code like bean creation. It may be useful in many cases for example enable/disable service if specific property is available. Below are the attributes which can be used for property check. havingValue - Provide the value which need to check against specified property otherwise it will check that value should not be false. matchIfMissing - If true it will match the condition and execute the annotated code when property itself is not available in environment. name - Name of the property to be tested. If you want to test single property then you can directly put the property name as string like "" and if you have multiple properties to test then you can put the names like {"prop.name1","prop.name2"} prefix - It can be use when you want to apply some prefix to

Entity to DTO conversion in Java using Jackson

It's very common to have the DTO class for a given entity in any application. When persisting data, we use entity objects and when we need to provide the data to end user/application we use DTO class. Due to this we may need to have similar properties on DTO class as we have in our Entity class and to share the data we populate DTO objects using entity objects. To do this we may need to call getter on entity and then setter on DTO for the same data which increases number of code line. Also if number of DTOs are high then we need to write lot of code to just get and set the values or vice-versa. To overcome this problem we are going to use Jackson API and will see how to do it with minimal code only. Maven dependency <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-databind</artifactId> <version>2.9.9</version> </dependency> Entity class Below is