Sākums Izpētīt Palīdzība
Reģistrēties Pierakstīties
crssadmin
/
crssconfig
1
0
Atdalīts 0
Faili Problēmas 0 Izmaiņu pieprasījumi 0 Vikivietne

Nav apraksta

Koks: 09d3b48f99
Atzari Tagi
crssconfig
ZIP TAR.GZ
Nas Villanueva 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-admin 318a68cf6b Remove per service hikari setting (adjust it when needed) 8 gadi atpakaļ
crss-data 318a68cf6b Remove per service hikari setting (adjust it when needed) 8 gadi atpakaļ
crss-dataflow-app 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-datainterface-task-ingest 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-metering 9e174962a2 Change logging level for metering 8 gadi atpakaļ
crss-meterprocess-app 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-meterprocess-stream-daily-sink 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-meterprocess-stream-mapper 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-meterprocess-stream-processor-daily-validate 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-meterprocess-stream-source-daily-raw 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-meterprocess-task-stlready 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-mq-computation 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-mtr 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-reg 01a6aeb88e Remove datasource driver in crss-reg-dev.yml 8 gadi atpakaļ
crss-sched 318a68cf6b Remove per service hikari setting (adjust it when needed) 8 gadi atpakaļ
crss-settlement-app 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-settlement-task-calculation 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-settlement-task-invoice-generation 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
crss-ui b6007ff967 Add pemc-uat config for crss-ui 8 gadi atpakaļ
ui-bsmd 09d3b48f99 Renamed application.yml to their respective application name 8 gadi atpakaļ
.gitignore 07d2f1ea8b Updated gitignore 9 gadi atpakaļ
README.md 968c20c111 Test commit. 9 gadi atpakaļ
application-dev.yml 3c398d8568 Change top datasource to use EnterpriseDB with config of 1 db multiple schema 8 gadi atpakaļ
application-pemc-uat.yml a1be03dd14 Config - Added driver config for pemc-uat env 8 gadi atpakaļ
application-ss-combined.yml bb55d024b0 Temporary set ss-combined profile to postgres driver 8 gadi atpakaļ
application-staging.yml f397cb6491 Remove duplicates setting of sec server url 8 gadi atpakaļ
application.yml cf7e288f31 Update default connection pooling - lower to half from default values 8 gadi atpakaļ

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