-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
- validate_legacy_params return 1 kills the pod (use mysql1 as name not mysql). Or use DATASOURCES without XX_SERVICE_HOST, XX_SERVICE_PORT or XX_DATABASE
- if you add a PG and MYSQL db and there's a problem with the MYSQL config you get duplicate copies of PG which blows up on start for duplicate resources
- TX datasource is always the 2nd datasource regardless of TX_DATABASE_PREFIX_MAPPING
- Limited to one instance of each db type
- clones
-
CLOUD-1619 [EAP6] fix datasource issues
- Closed