-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(persistence): set postgres ssl config to string Fixes #1866 #1867
Conversation
It seems like you used an old branch to make these changes, causing a lot of conflicts and old commits to be included. Can you redo your changes on a new branch that is checked out from a fresh pull of master? After you can force push the changes to this branch or open a new PR with the new branch. |
I tested this on our cluster using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, please keep support for SSL
and introduce SSLMode
.
As discussed the following changes enable the following behavior:
Here are some example values if you were using an Argo helm chart argo:
controller:
persistence:
ssl: true
sslMode: "verify-full" According to the pq code docs I could find the following values are supported for
|
Server suite tests are failing. Something about a
|
@AntoineDao lets try updating your branch... |
Codecov Report
@@ Coverage Diff @@
## master #1867 +/- ##
=========================================
Coverage ? 11.69%
=========================================
Files ? 72
Lines ? 28894
Branches ? 0
=========================================
Hits ? 3378
Misses ? 25072
Partials ? 444
Continue to review full report at Codecov.
|
|
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
. Why? for the release notes.Fixes #1866