Home Esplora Aiuto
Registrati Accedi
crssadmin
/
crssconfig
1
0
Forka 0
File Problemi 0 Pull Requests 0 Wiki

Nessuna descrizione

Albero (Tree): 5c13fe448d
Rami (Branch) Tag
crssconfig
ZIP TAR.GZ
Chris Lim 5c13fe448d Modified scheduler config 9 anni fa
crss-admin d584e20810 LDAP / master - Added config for switchable password operation 9 anni fa
crss-discovery 40c84af994 devops / master - moved all config to their respective app directory 9 anni fa
crss-metering 7f5462c016 Added psql mq config for staging and uat env. 9 anni fa
crss-reg a7c706e15d Configuration cleanup 9 anni fa
crss-sched 5c13fe448d Modified scheduler config 9 anni fa
crss-ui 28270d5b75 Added undertow definition. 9 anni fa
.gitignore 07d2f1ea8b Updated gitignore 9 anni fa
README.md 968c20c111 Test commit. 9 anni fa
application.yml b984be4a94 devops / master - Added global yml file for common configurations 9 anni fa

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