Skip to content

Require At Least One Repo to be Configured #2662

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

Merged
merged 1 commit into from
Sep 8, 2021

Conversation

andrewlecuyer
Copy link
Collaborator

At least one pgBackRest repository must be defined within a PostgresCluster spec for the proper operation of any/all PostgreSQL clusters created by PGO.

This commit therefore updates the validation for the repos section of the spec to require that at least one repo always
be defined when creating or modifying a PostgresCluster.

[ch12418]

@andrewlecuyer andrewlecuyer changed the title Require At Lead One Repo to be Configured Require At Least One Repo to be Configured Sep 2, 2021
At least one pgBackRest repository must be defined within a
PostgresCluster spec for the proper operation of any/all
PostgreSQL clusters created by PGO.

This commit therefore updates the validation for the "repos"
section of the spec to require that at least one repo always
be defined when creating or modifying a PostgresCluster.

Issue: [ch12418]
@tjmoore4 tjmoore4 merged commit eb994a3 into CrunchyData:master Sep 8, 2021
@james-callahan
Copy link

I'm not sure this was the correct fix: why should I have to have a repo configured if I don't want backups?
As mentioned in #2531:

archive_command to /bin/true when there are no backup repos

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.

4 participants