crssadmin/crssconfig @ 4df876887d42d02e5772756e3e04f3fe7c07588d

Nav apraksta

1 Atzari

Monte Cillo Co 4df876887d Remove crss-admin ds duplicate config		8 gadi atpakaļ
crss-admin	4df876887d Remove crss-admin ds duplicate config	8 gadi atpakaļ
crss-data	9efb641636 data-extraction config	8 gadi atpakaļ
crss-metering	8f656f5e44 DevOps - Renamed config prefix in preparation for Cloud Bus Per App Propagation	8 gadi atpakaļ
crss-reg	a5fd0e0f76 Update dev profile - point root dir to /tmp from relative target folder	8 gadi atpakaļ
crss-sched	8bb96995f0 Revert "Point staging profile database to another postgres service"	8 gadi atpakaļ
crss-ui	8f656f5e44 DevOps - Renamed config prefix in preparation for Cloud Bus Per App Propagation	8 gadi atpakaļ
.gitignore	07d2f1ea8b Updated gitignore	9 gadi atpakaļ
README.md	968c20c111 Test commit.	9 gadi atpakaļ
application-dev.yml	cd1218dc8e External global config per profile	8 gadi atpakaļ
application-pemc-staging.yml	cd1218dc8e External global config per profile	8 gadi atpakaļ
application-staging.yml	cd1218dc8e External global config per profile	8 gadi atpakaļ
application-uat.yml	cd1218dc8e External global config per profile	8 gadi atpakaļ
application.yml	bc1c5943e9 Add postgres and jpa config to global since we're using postgres	8 gadi atpakaļ

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:

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.
Spring profile To load a spring profile: -Dspring.cloud.config.profile=

There should also be a corresponding file in the git repository with the format -.yml

README.md