postgres: add WITH
tls options
#6787
Closed
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.
This PR depends on changes to
rust-postgres
that are currently PR'd to the upstream project. 3fcde15 pulls in the changes based on top of the HEAD of our fork.The logic to configure the
SslConnector
is part ofrust-postgres/postgres-openssl
(see linked PR). I found it hard to justify why we would want to have the additional sslmodes upstream without an easy way to make use of them upstream. If there are concerns about the changes upstream, we should be able to easily pull them into our repo.Users can now specify TLS configuration as in:
The key names are based on the official Postgres keys.