Add support to client SSL PEM cert and key and root CA PEM cert #2390
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.
PR Info
Currently if you want to use SSL client certificate and key you can currently do it via a few options:
PgPool
orMySqlPool
and create aDatabaseConnection
.A. You can set
sslrootcert=PATH
,sslkey=PATH
,sslca=PATH
in the URI params.B. You can set env variables
PGSSLCERT=PATH
,PGSSLKEY=PATH
,PGSSLROOTCERT=PATH
ssl-cert
,ssl-key=PATH
,ssl-ca=PATH
in the URI paramsBoth
3
and2
require you to mount the keys/certs to a volume and pass a PATH to that.Only 1 allows you to pass the certs/keys themselves which allows nicer integrations with KMS/Secret Manager but comes at the cost of building the pools yourself,
Which is why I only added the
_pem
variants ofsqlx