-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ feature: integrate SSL mode for PG connections #77
Conversation
thx can you deposit some test for it, which will test the effect of the code change |
2b82292
to
75c3314
Compare
I've integrate a test for this change that checks the behavior. What do you think? |
looks okay |
@r-52 could you add the new configuration possibility in the readme after that i will merge everything |
@r-52 could you do this? |
@ReneWerner87 sorry, I missed the ping :/ I'll take a look at it and ping you when it's done |
ok :D |
@r-52 and don´t forget to resolve the merge conflicts by updating your branch |
Right now, the default connection for postgres is `disable`. Some databases require `verify` or even `required`. This PR introduces a new implementation that allows the user to override the `disable` mode. The PR keeps a backwards compatible config entry, that sets the default behavior to `disable` if it's missing.
75c3314
to
4ea7d71
Compare
@ReneWerner87 Sorry for the delay. The conflict is resolved and I've added a new README entry for the new configuration option 👍 |
Right now, the default connection for postgres is
disable
. Some databases requireverify
or evenrequired
. This PR introduces a new implementation that allows the user to override thedisable
mode. The PR keeps a backwards compatible config entry, that sets the default behavior todisable
if it's missing.