This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
EVEREST-316 backup for not existing cluster #153
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
oksana-grishchenko
requested review from
gen1us2k and
recharte
as code owners
recharte
approved these changes
Sep 13, 2023
…ing-cluster' into EVEREST-316-backup-for-not-existing-cluster
oksana-grishchenko
deleted the
EVEREST-316-backup-for-not-existing-cluster
branch
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.
Check DatabaseCluster existance
Problem:
EVEREST-316
Now it's not possible to create a backup for non-existing db cluster
CHECKLIST
Jira
Tests