Nav apraksta

Monte Cillo Co a0bbb358fe Organize admin service config 9 gadi atpakaļ
crss-admin a0bbb358fe Organize admin service config 9 gadi atpakaļ
crss-discovery 40c84af994 devops / master - moved all config to their respective app directory 9 gadi atpakaļ
crss-metering 15d27ca78c Move shareable config to global yml 9 gadi atpakaļ
crss-reg f974ae4357 Move metering's oauth config to global yml 9 gadi atpakaļ
crss-sched 5c13fe448d Modified scheduler config 9 gadi atpakaļ
crss-ui 28270d5b75 Added undertow definition. 9 gadi atpakaļ
.gitignore 07d2f1ea8b Updated gitignore 9 gadi atpakaļ
README.md 968c20c111 Test commit. 9 gadi atpakaļ
application.yml a0bbb358fe Organize admin service config 9 gadi atpakaļ

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