Support setting ssl client certificate information via environment variables #574
+145
−26
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.
What
We'd like to support setting ssl certificate information via environment variables.
How
get_connect_options
, which will read both the uri and the ssl information, and use it andconnect_with
everywhere instead ofconnect
with just theuri
. We make sure all operations using configuration version 5 including the connector and the cli useget_connect_options
(except tests).client_cert
,client_key
androot_cert
from the environment and put them directly into the sqlx connection options.How we tested this
We used this article as a guide on how to set up postgres+certs with docker.
After running all of the commands, we had to do the following as well:
Then, we added the following environment variables:
Initialized and updated the connector:
Added a native query:
Started the connector:
CONNECTION_URI="postgresql://postgres:postgres@localhost:64009/postgres?sslmode=verify-ca" target/debug/ndc-postgres serve --configuration /tmp/ssltest
And ran a query: