feat(postgres): Support manual postgres certificate deployment #186
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.
Description of Changes
Postgres TLS certificates are read from a secret set using the
backend.postgres.sslsecret.name
option. Some users need to manage their certificate injection using an alternative to secrets, usually a system specific to their company.This change allows users to opt into disabling reading from a secret by introducing a new option
backend.postgres.source
with valid values ofsecret
andmanual
. Defaults tosecret
. When `manual, reading the TLS certificates from a secret will be skipped.Please check that the PR fulfills these requirements