Strona główna Odkrywaj Pomoc
Zarejestruj się Zaloguj się
crssadmin
/
crssconfig
1
0
Forkuj 0
Pliki Problemy 0 Oczekujące zmiany 0 Wiki

Brak opisu

Drzewo: 49ae55d3c1
Gałęzie Tagi
crssconfig
ZIP TAR.GZ
jdogillo 49ae55d3c1 test fix get top level driver class 8 lat temu
crss-admin 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-audit 49ae55d3c1 test fix get top level driver class 8 lat temu
crss-data 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-dataflow-app 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-datainterface-app 6f3e6e64a4 dev2 updates 8 lat temu
crss-datainterface-task-ingest 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-edge 8c552c6f25 Update crss-edge for new data-interface-app 8 lat temu
crss-metering 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-meterprocess-app 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-meterprocess-stream-daily-sink 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-meterprocess-stream-mapper 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-meterprocess-stream-processor-daily-validate 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-meterprocess-stream-source-daily-raw 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-meterprocess-task-stlready 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-mq-computation 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-mtr 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-reg 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-sched 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-settlement-app 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-settlement-task-calculation 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-settlement-task-calculation-addtlcomp 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-settlement-task-file-gen-addtlcomp 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-settlement-task-invoice-generation 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-settlement-task-validation 0ec7a252b1 apply prod datasource credentials in top-level configs 8 lat temu
crss-uaa 6f3e6e64a4 dev2 updates 8 lat temu
crss-ui b4e7b52b6d Merge branch '2.0.x' into 2.1.x 8 lat temu
ui-bsmd b4e7b52b6d Merge branch '2.0.x' into 2.1.x 8 lat temu
.gitignore a850409a21 add redis to devlocal 8 lat temu
README.md 968c20c111 Test commit. 9 lat temu
application-azure.yml fe98f74c2e [Devops] Reverted some changes but removed extra /uaa 8 lat temu
application-client-sec.yml 52feed7329 [Devops] Removed extra /uaa path in client-sec 8 lat temu
application-dev.yml 0b8f847b96 Change top datasource to use EnterpriseDB with config of 1 db multiple schema 8 lat temu
application-pemc-top-sit.yml 753f2ac3cc add application-pemc-top-sit.yml 8 lat temu
application-pemc-uat-default.yml 4fac14be90 corrected rabbit url for pemc-uat-default 8 lat temu
application-pemc-uat-sit.yml 79fc7e19b1 fixed 154081 8 lat temu
application-pemc-uat.yml d371b28d30 Config - Added driver config for pemc-uat env 8 lat temu
application-ss-combined.yml b4e7b52b6d Merge branch '2.0.x' into 2.1.x 8 lat temu
application-staging.yml 60c61ae0ec Remove duplicates setting of sec server url 8 lat temu
application-top-sit.yml c0f644189c added top-sit configurations for p1 and p2 8 lat temu
application.yml 087dcf55c4 [Devops] Removed security in root config 8 lat temu

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