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.
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
fix(pg-connection-string): get closer to libpq semantics for
sslmode
#2709base: master
Are you sure you want to change the base?
fix(pg-connection-string): get closer to libpq semantics for
sslmode
#2709Changes from 1 commit
440b6d9
f1a6059
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, even though libpq has and has documented this same problem, maybe we should enforce that
config.ssl.ca
is truthy here.The main issue with this would be for anyone who wants to add a
ca
key to the returnedconfig.ssl
after parsing. I don’t think a warning is the way to go (too easy for those who need it to miss or ignore, and annoying for those who don’t need it to suppress). Would adding a whole options parameter to support this (parse(str, {deferSslCa: true})
– probably a better name option) be too much? (Related issue, merging configuration with a connection string is hard in general: #3327)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively, the check could go in pg, e.g. by pg-connection-string exporting
const NO_VERIFY = () => {}
and pg throwing ifconfig.ssl.checkServerIdentity === NO_VERIFY && !config.ssl.ca
.