You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Missing an example (or description) how to use the connector in a real munit-test.
When I simply add the connector (e.g. for a postgres-testcontainer) an instance is started, the init-script is executed, but the flow under test cannot access this database, because ports are defined dynamically in testcontainer and therefore no configuration is possible.
tescontainer-jdbc itself ignores all ports provided in the url, so it cannot be provided from the test itself.
The text was updated successfully, but these errors were encountered:
When your flow runs and Database connector tries to connect using jdbc url, connector will spin up a database in a container and provide a connection to that. Let me know if you have any questions.
Missing an example (or description) how to use the connector in a real munit-test.
When I simply add the connector (e.g. for a postgres-testcontainer) an instance is started, the init-script is executed, but the flow under test cannot access this database, because ports are defined dynamically in testcontainer and therefore no configuration is possible.
tescontainer-jdbc itself ignores all ports provided in the url, so it cannot be provided from the test itself.
The text was updated successfully, but these errors were encountered: