feat: extra database connection properties #34
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added an option to set extra client properties when connecting to the database. This is primarily needed so that SSL/TLS can be used to connect to the database.
This change should be backwards compatible as well as if no props are set, it just won't set anything and behave exactly as it does now.
Fixes #28
I wasn't sure of a good way to test this because I couldn't find a way to get the PostgreSQL testcontainer to use TLS.
Note: this doesn't solve the issue of custom CA's that was discussed in #28, but at least we can turn SSL/TLS on. It's a start...