Skip to content

Commit

Permalink
Fix references to keys in S3 credential secret for backups
Browse files Browse the repository at this point in the history
  • Loading branch information
bbliem committed Aug 14, 2024
1 parent ad8880d commit 2577a67
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion charts/django/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ type: application
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 0.6.2
version: 0.6.3

# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Versions are not expected to
Expand Down
4 changes: 2 additions & 2 deletions charts/django/templates/db/cluster.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -46,10 +46,10 @@ spec:
s3Credentials:
accessKeyId:
name: {{ $pgbackup.s3Secret.name | required "Value db.cluster.backup.s3Secret.name required" }}
key: {{ $pgbackup.accessKeyName }}
key: {{ $pgbackup.s3Secret.accessKeyName }}
secretAccessKey:
name: {{ $pgbackup.s3Secret.name }}
key: {{ $pgbackup.secretAccessKeyName }}
key: {{ $pgbackup.s3Secret.secretAccessKeyName }}
{{- end }}
{{/* TODO: How to enable this safely? */}}
{{- if .Values.db.cluster.bootstrapRecovery.enabled }}
Expand Down

0 comments on commit 2577a67

Please sign in to comment.