crssadmin/crssconfig @ 99a31f868e4eaa0d419a1da5ea5f430ff54604f4

Bez popisu

1 Větve

Julius Cessar Lapugot 99a31f868e [BCQ] Change query for checking record if it exists		před 9 roky
crss-admin	0ec13b218e infra / develop - Added gzip config from app repo	před 9 roky
crss-discovery	40c84af994 devops / master - moved all config to their respective app directory	před 9 roky
crss-metering	99a31f868e [BCQ] Change query for checking record if it exists	před 9 roky
crss-reg	0ec13b218e infra / develop - Added gzip config from app repo	před 9 roky
crss-ui	0ec13b218e infra / develop - Added gzip config from app repo	před 9 roky
.gitignore	07d2f1ea8b Updated gitignore	před 9 roky
README.md	c0d8bd4e97 Mini guide on how to configure Spring Cloud Config.	před 9 roky
application.yml	b984be4a94 devops / master - Added global yml file for common configurations	před 9 roky

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