Brak opisu

rfetalveroiii 8f5daaa256 PEMBOARD and MSP email add address for BCC entry 8 lat temu
crss-admin 8f5daaa256 PEMBOARD and MSP email add address for BCC entry 8 lat temu
crss-data 59e803d7a1 Externalize crss-data config per env 8 lat temu
crss-metering 1f7b2ced77 Remove crss-metering ds duplicate config 8 lat temu
crss-reg a9a0d674fb Remove extra character causing to fail retrieval of config 8 lat temu
crss-sched f3c29a6cc8 Externalize crss-sched config per env 8 lat temu
crss-ui 8f656f5e44 DevOps - Renamed config prefix in preparation for Cloud Bus Per App Propagation 8 lat temu
.gitignore 07d2f1ea8b Updated gitignore 9 lat temu
README.md 968c20c111 Test commit. 9 lat temu
application-dev.yml cd1218dc8e External global config per profile 8 lat temu
application-pemc-staging.yml cd1218dc8e External global config per profile 8 lat temu
application-staging.yml cd1218dc8e External global config per profile 8 lat temu
application-uat.yml 2a2792a18c Remove redis from global config and replace uat redis host to redis hostname 8 lat temu
application.yml bc1c5943e9 Add postgres and jpa config to global since we're using postgres 8 lat temu

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