Tidak Ada Deskripsi

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

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