Нема описа

Monte Cillo Co f3c29a6cc8 Externalize crss-sched config per env пре 8 година
crss-admin 4df876887d Remove crss-admin ds duplicate config пре 8 година
crss-data 59e803d7a1 Externalize crss-data config per env пре 8 година
crss-metering 1f7b2ced77 Remove crss-metering ds duplicate config пре 8 година
crss-reg 821d802789 Remove crss-reg ds duplicate config пре 8 година
crss-sched f3c29a6cc8 Externalize crss-sched config per env пре 8 година
crss-ui 8f656f5e44 DevOps - Renamed config prefix in preparation for Cloud Bus Per App Propagation пре 8 година
.gitignore 07d2f1ea8b Updated gitignore пре 9 година
README.md 968c20c111 Test commit. пре 9 година
application-dev.yml cd1218dc8e External global config per profile пре 8 година
application-pemc-staging.yml cd1218dc8e External global config per profile пре 8 година
application-staging.yml cd1218dc8e External global config per profile пре 8 година
application-uat.yml cd1218dc8e External global config per profile пре 8 година
application.yml bc1c5943e9 Add postgres and jpa config to global since we're using postgres пре 8 година

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