crssadmin/crssconfig @ f3c29a6cc895ec4d1504db6b149510ed0442ad1c

Nessuna descrizione

179 Commit

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

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