fix: we use sslmode not pgsslmode in the deploy repos#957
fix: we use sslmode not pgsslmode in the deploy repos#957Chickensoupwithrice merged 3 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
jdpleiness
left a comment
There was a problem hiding this comment.
Are we sure about that? I'm seeing this used a lot: https://sourcegraph.sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+PGSSLMODE&patternType=keyword&sm=0
|
ahhh, fuck 🤔 |
|
I think the Helm chart values key is |
|
Yeah, I think I actually need to change the helm values file. Strange that it worked in my testing though? 🤔 |
|
Hm, I'm curious how it'd have worked?
… Message ID: ***@***.***>
|
|
It works because the there's a helper template that applies a prefix On second thought, the docs need to reflect the difference between helm chart and env var? Need to think about this more. |
Key = apiVersion: v1
kind: Secret
...
data:
...
pgsslmode: "require" # optional, enable if using SSLKey = Current Helm template helper function: - name: {{ printf "%sSSLMODE" $prefix }}
valueFrom:
secretKeyRef:
key: sslmode
name: {{ $secretName }}Current Helm chart pgsql secret template {{- if not .Values.pgsql.auth.existingSecret }}
apiVersion: v1
kind: Secret
...
data:
...
sslmode: {{ .Values.pgsql.auth.sslmode | toString | b64enc | quote }} |
MaedahBatool
left a comment
There was a problem hiding this comment.
LGTM @Chickensoupwithrice feel free to merge. :)
marcleblanc2
left a comment
There was a problem hiding this comment.
AFAIA, there needs to be a different xSSLMODE env var for each database, matching the same prefix as the other env vars for the same db.
The Helm values key, however is sslmode
The docs must match this.
|
Thank you @marcleblanc2 🙏🏽 I addressed your comments |
addressed comments
@marcleblanc2 pointed this out: https://linear.app/sourcegraph/issue/REL-638/configure-aws-rds-databases-for-tls-connections-in-helm-chart
Pull Request approval
You will need to get your PR approved by at least one member of the Sourcegraph team. For reviews of docs formatting, styles, and component usage, please tag the docs team via the #docs Slack channel.