Skip to content

Conversation

@jasonchung1871
Copy link

Made changes to make the crunchy repos more configurable and updated the README.

We can create the schedule in the values.yaml file allowing us to dynamically add repos with: name
path
volume
s3
schedules

Made changes to make the crunchy repos more configurable. Updated the README.

We can create the schedule in the values.yaml file allowing us to dynamically add repos with:
name
path
volume
s3
schedules
{{ if .Values.postGISVersion }}
postGISVersion: {{ .Values.postGISVersion | quote }}
{{ end }}
postgresVersion: {{ .Values.postgresVersion }}
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate postgresVersion

repo2-s3-uri-style: {{ .Values.pgBackRest.s3.s3UriStyle }}
{{- end }}
{{ range $repo := .Values.pgBackRest.repos }}
{{ if eq $.Values.pgBackRest.s3.enabled true }}
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could probably be changed to check if the s3 key exists, using this check for the bucket path, also did not want to change the other uses of s3.enabled

Removed app specific values
@jasonchung1871
Copy link
Author

@caggles this is currently working in our namespace! i'm just looking into porting over our data from an older postgres database into the crunchy database now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant