Spring Cloud Config Server Shared Properties Across Applications

spring properties spring-cloud spring-cloud-config
Jeffxor picture Jeffxor · Apr 21, 2015 · Viewed 8.3k times · Source

I currently have a number of deployable applications that work in a distributed fashion to solve a business problem. We are currently using a number of property configuration files to provide changing configuration per environment based off a system environment variable. All these deployable application share common configuration for database and messaging. This is currently achieved by picking up property files from the class path and having both deployed apps share a common jar for each connection (db, jms) containing property files.

I am looking to start using Spring Config Server to externalize this configuration if possible. I have a question about how to share this common config.

Currently it looks something like this:-

Web1
- database
- jms

Messaging1
- database
- jms

In this situation both deployed apps share the same connections and these connections change per environment (lab, prf, prd, etc). How can I achieve the same with the Spring Configuration Server where I have app config for each deployable app?

Application.yml
Web1.yml
Web1-dev.yml
Messaging1.yml
Messaging1-dev.yml

If a connection property changed for an environment I would need to make the change to each deployable app configuration rather than making it just once.

Is there currently anyway to achieve this? Am I just missing a simple point?

Answer

Wojciech Wirzbicki picture Wojciech Wirzbicki · Feb 21, 2018

I found working solution here https://cloud.spring.io/spring-cloud-config/single/spring-cloud-config.html, paragraph "2.1.5 Sharing Configuration With All Applications". It says:

With file-based (i.e. git, svn and native) repositories, resources with file names in application* are shared between all client applications (so application.properties, application.yml, application-*.properties etc.). You can use resources with these file names to configure global defaults and have them overridden by application-specific files as necessary.

You should create application.properties or application.yml at the top level of configuration repository (if it is git or svn based). Don't forget to commit the changes.

Related questions

Access properties file programmatically with Spring?

We use the code below to inject Spring beans with properties from a properties file. <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> <property name="locations" value="classpath:/my.properties"/> </bean> <bean id="…

Read More
Is there a way to specify a default property value in Spring XML?

We are using a PropertyPlaceholderConfigurer to use java properties in our Spring configuration (details here) eg: <foo name="port"> <value>${my.server.port}</value> </foo> We would like to add an additional …

Read More
Using multiple property files (via PropertyPlaceholderConfigurer) in multiple projects/modules

We are currently writing an application which is split into multiple projects/modules. For example, let's take the following modules: myApp-DAO myApp-jabber Each module has its own Spring context xml file. For the DAO module I have a PropertyPlaceholderConfigurer which …

Read More