So I recently learned this awesome config service of Spring Cloud, and after some struggling I\'m able to get our distributed application set up, with multiple nodes reading con
OK, after some more research I found the answer. From https://docs.pivotal.io/spring-cloud-services/config-server/configuration-clients.html
A Spring application can use a Config Server as a property source. Properties from a Config Server will override those defined locally (e.g. via an application.yml in the classpath).
So the right thing to do is to leave any client side property out of the config service. This to me also means for such properties there is no way to have a default that will only be overwritten if a client side value presents, which would be good to have.