Support ssl and ssl_opts connection options#14
Conversation
|
@Ziinc @filipecabaco sorry to ping you, I was wondering if this PR could be reviewed. We have a change we are looking to merge into NervesHub (nerves-hub/nerves_hub_web#1151) and it would be great to not use my fork. p.s. such a god damn smart use of postgres for node discovery! |
|
@joshk could you add in some docs around the ssl options and example usage, as well as bump the patch version? |
|
Thanks for the quick reply @Ziinc Done! Let me know if you want something with extra detail. |
Ziinc
left a comment
Ziinc
left a comment
There was a problem hiding this comment.
LGTM, will only be able to publish this on 29th
|
Awesome, thank you! |
|
@Ziinc Happy New Year! any chance of having this merged? |
|
hey! just a quick heads up that I'll review this one today. sorry for the delay 🙏 |
|
@filipecabaco thanks for the quick reply! |
3 participants
What kind of change does this PR introduce?
This adds support for the
sslandssl_optsPostgrex connection options.What is the current behavior?
If a custom SSL cert is required then the connection will fail.
What is the new behavior?
Custom SSL certs can now be configured and used.
Additional context
Crunchy Bridge provides customers their own SSL PEM, and SSL is enforced with all db connections. This PR addresses issues with SSL details not being passed to Postgrex.