This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
EVEREST-827-pg-repos-validation #429
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # api/validation.go
ghost
approved these changes
Feb 9, 2024
recharte
approved these changes
Feb 9, 2024
Co-authored-by: Diogo Recharte <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PG repos amount validation
Problem:
EVEREST-827
PG cluster has the limitation - it must have no more than 4 repos defined. Each schedule is considered as a different repo, as well as any new bucket which wasn't in use before. Also we have a "technical" repo1 which is used to run the cluster and takes one slot, so the enduser can configure max 3 repos.
Solution:
Validate that there is no more than 3 schedule and no more than 3 different backup storages used
CHECKLIST
Jira
Tests