No Description

Chris Lim a7c706e15d Configuration cleanup 9 years ago
crss-admin a7c706e15d Configuration cleanup 9 years ago
crss-discovery 40c84af994 devops / master - moved all config to their respective app directory 9 years ago
crss-metering a7c706e15d Configuration cleanup 9 years ago
crss-reg a7c706e15d Configuration cleanup 9 years ago
crss-ui 0ec13b218e infra / develop - Added gzip config from app repo 9 years ago
.gitignore 07d2f1ea8b Updated gitignore 9 years ago
README.md c0d8bd4e97 Mini guide on how to configure Spring Cloud Config. 9 years ago
application.yml b984be4a94 devops / master - Added global yml file for common configurations 9 years ago

README.md

NOTES:

Default config should be for the current deployment environment (e.g. Staging or Production). The reason being, it should not require additional command line config to run the services. Developers should instead specify the additional command line config when executing the services.

These are the options for the developers:

  1. git branch Spring Cloud Config is able to handle git branches. This config is ideal if you have config experimentation and don't want to impact other developers. Specify -Dspring.cloud.config.label= when running the service.

  2. Spring profile To load a spring profile: -Dspring.cloud.config.profile=

  3. There should also be a corresponding file in the git repository with the format -.yml