You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

For an explanation about spring cloud config see http://cloud.spring.io/spring-cloud-config/spring-cloud-config.html 

 

Blueriq uses spring cloud config (besides the all the other functionality that spring cloud config uses) for changing/reloading settings via the development plugin.

In the configured folder one can place a application.properties and/or application-debug.properties (and yaml variants) because the default name is application (can be configured via spring.application.name=application) These are the files that can be edited by the development plugin

Notes:

to be able to edit settings via the development plugin the profile native must also be passed.

To refresh, inject the RefreshScope, dont call the urls

1. Client

 

Spring config client is integrated in the blueriq-web.

Client config options

bootstrap.properties

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

* To make a connection to cloud config server, see #gitbasicauth

application.properties will not contain any property meant for the config client

2. Server

Spring config server will 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.

 

bootstrap.properties

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

* Indicates that the server should read it’s own application.properties from the remote config server (GIT or filesystem)

 

bootstrap.properties - extended for using the file-system

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

 

bootstrap.properties - extended for using GIT - basic authentication 

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

 

application.properties

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

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

 

Repository structure

TODO - ongoing discussion

Branch per environment?

Branch per version?

 

  • No labels