Начало Каталог Помощ
Регистрация Вход
crssadmin
/
crssconfig
1
0
Разклонения 0
Файлове Задачи 0 Заявки за сливане 0 Уики

Няма описание

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

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