For an explanation on Spring Cloud Config see http://cloud.spring.io/spring-cloud-config/spring-cloud-config.html 

The runtime Runtime uses Spring Cloud Config to be able to load properties from a remote configuration server.

By default the runtime is packaged with an embedded configuration server. This embedded server is configured serve a set of property files located on the file system. Because the server is embedded, the cloud config client does not need to be configured with a remote uri of the configuration server. Instead the client will automatically load its configuration from the embedded config server.

For the embedded config server the following properties are configured:

spring.profiles.active=native 
spring.cloud.config.server.native.searchLocations=${spring.config.location}
spring.cloud.config.server.bootstrap=true

By specifying the for changing and reloading properties. In the configured folder (

...

 may be placed with properties to configure the runtime.

Client Config

Spring config client is integrated in the blueriq-runtime.

...

In order to connect to a remote server instead of the embedded server, the following properties can be set in a file named bootstrap.properties at the 

spring:
  cloud:
    config:
      uri: http://localhost:8888
      username: .cloud.config.uri=<cloud-server-uri>
spring.cloud.config.username=<cloud-server-username> (*)
      password: spring.cloud.config.password=<cloud-server-password> (*)
      failFast: true
      retry:
        max-attempts: 10
        initial-interval: 5000
        max-interval: spring.cloud.config.failFast=true
spring.cloud.config.retry.max-attempts=10
spring.cloud.config.retry.initial-interval=5000
spring.cloud.config.retry.max-interval=10000

* To make a connection to cloud config server, see #scsauth
Include Page_PropertiesFileJava_PropertiesFileJava will not contain any property meant for the config client

...

Server Config

Spring config server will can run separately and handle the property files. The client will communicate with the server to get the property files.

The property files will either come from the file-system or use GIT.

encrypt:
  failOnError: .failOnError=false
  key: "IGotTheKey"
  encrypt.key=IGotTheKey
encrypt.key-store:
    secret: "IGotTheSecret"
spring:
  cloud:
    config:
      server:
        bootstrap: .secret=IGotTheSecret
spring.cloud.config.server.bootstrap=true (*)

* Indicates that the server should read it’s own

spring:
  profiles:
    active: native
  cloud:
    config:
      server:
        native:
          searchLocations: file:D:/local-properties.profiles.active=native
spring.cloud.config.server.native.searchLocations

spring:
  cloud:
    config:
      server:
        git:
          uri: .cloud.config.server.git.uri=https://git.blueriq.com/config-repo.git
          basedir: target/config
          username: <git_username>
          password: spring.cloud.config.server.git.basedir=target/config
spring.cloud.config.server.git.username=<git_username>
spring.cloud.config.server.git.password=<git_password>

server:
  port: .port=8888
security:
  user:
    name: .user.name=<username> (*)
    password: security.user.password=<password> (*)
management:
  .context-path: =/admin

 * Username and password that will be used for the client to connect to this server.

Further reading

Reading properties from file system

Reading properties from GIT

...