Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
False
-
Undefined
-
-
Description
The EAP documentation says you can define datasources with ENV variables and a PREFIX. For example:
DB_SERVICE_PREFIX_MAPPING=test-mysql=TEST1
This works as expected except in two cases.
The prefix is not being honored when I define SERVICE_HOST or SERVICE_PORT.
TEST1_SERVICE_HOST=abcd TEST1_SERVICE_PORT=1234
The container spins up and says those two fields are missing, so it will not create the datasource.
The only accepted format is the fully qualified pool name.
TEST_MYSQL_SERVICE_HOST=abcd TEST_MYSQL_SERVICE_PORT=1234
Note that pretty much all the other datasource properties follow the PREFIX convention, so it's confusing to end-users as to why these 2 properties need to be treated differently.
I looked at the Git repository and saw all the tests are written as if the PREFIX is not allowed on these 2 fields. The documentation needs to explicitly call this out if this is a technical limitation.