Page History
The spring cloud config server reads its values from file system (possibly on one central location). It is possible to stop using files on the filesystem, and read property files out of gitGit. This has advantages also the properties are version managed using a standard approach.
To be able to do this, these change have to be made:
bootstrap.properties
- for using the file system
Code Block |
---|
spring: profiles: active: native cloud: config: server: native: searchLocations: .profiles.active=native spring.cloud.config.server.native.searchLocations=file:D:/local-properties |
bootstrap.properties
- for using GIT Git - basic authentication
Code Block |
---|
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: <git_password> |
UI Text Box |
spring.cloud.config.server.git.basedir=target/config
spring.cloud.config.server.git.username=<git_username>
spring.cloud.config.server.git.password=<git_password> |
Note |
---|
Please note that when using GITGit, the development plugindashboard has limited functionality. As properties can only be read from GITGit and not written, the development tools plugin can only read values and not write them. Any changes made with the development toolbardashboard may work during your session, but starting a new session or reloading the application will read the original values from GITGit again. For shortcut properties, they will not even be updated in your current session. This is only an issue for development or test environments, as the development tools plugin isshould not presentbe enabled on production environments. |