Update default configuration for ssl to 'allow' #15917
Merged
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 does this PR do?
This updates the default config for
ssl
fromdisable
toallow
. The reason is that postgres 15 on RDS is switching the default forforce_ssl
totrue
. Setting the default toallow
means that a failure to connect without ssl will trigger an attempt to connect using ssl.We could also consider going a bit further and setting the default to
prefer
which means ssl would be used first but I went with a more conservative approach that's closer to our current value (prefer non-ssl and switch to ssl on failure).Motivation
Help make for a smoother transition for RDS Postgres users when they upgrade to postgres 15.
Additional Notes
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.