Done
Details
Assignee
Adam DickmeissAdam DickmeissReporter
Adam DickmeissAdam DickmeissLabels
Priority
P2Story Points
2Sprint
NoneDevelopment Team
Core: PlatformFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Adam Dickmeiss
Adam DickmeissReporter
Adam Dickmeiss
Adam DickmeissLabels
Priority
Story Points
2
Sprint
None
Development Team
Core: Platform
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 4, 2021 at 9:17 AM
Updated April 12, 2021 at 8:07 AM
Resolved March 22, 2021 at 6:23 PM
Remove
PostgresTesterEmbedded
Remove
PostgresClient.getEmbeddedPort
andPostgresClient.setEmbeddedPort
Previously,
PostgresClient.init
would shift to "embedded" postgres if "host" config was absent.There are two options for what happens when host is not configured.. This would previously auto-enable embedded postgres.
1: Fail. This will make a module fail if it's started on its own without at least host configured (port probably defaults to 5432). Since init is not called until tenant init,
RestVerticle
should make a check already there (so the problem is seen at launch, not at tenant init).2. Accept.. init will just keep settings as they are and leave it to the Postgres client driver to determine what goes on.. (Probably defaults to localhost or local socket??). No change in behavior in start up ..The real change will not be seen until tenant init.. Where it will now try a "local" postgres and not spawn an embedded tester.
RestVerticle: Command line option embed_"postgres=true" should result in failure as this can not be honored anymore.