Home Explore Help
Register Sign In
crssadmin
/
crssconfig
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki

No Description

Tree: 8f656f5e44
Branches Tags
crssconfig
ZIP TAR.GZ
Nas Villanueva 8f656f5e44 DevOps - Renamed config prefix in preparation for Cloud Bus Per App Propagation 8 years ago
crss-admin a5fd0e0f76 Update dev profile - point root dir to /tmp from relative target folder 8 years ago
crss-metering 8f656f5e44 DevOps - Renamed config prefix in preparation for Cloud Bus Per App Propagation 8 years ago
crss-reg a5fd0e0f76 Update dev profile - point root dir to /tmp from relative target folder 8 years ago
crss-sched 8bb96995f0 Revert "Point staging profile database to another postgres service" 8 years ago
crss-ui 8f656f5e44 DevOps - Renamed config prefix in preparation for Cloud Bus Per App Propagation 8 years ago
.gitignore 07d2f1ea8b Updated gitignore 9 years ago
README.md 968c20c111 Test commit. 9 years ago
application.yml 4bfa5367d1 Service Discovery Removal 8 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