feat: halodb Create backup functionality #267
Draft
Conversation
This file contains hidden or 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
binbin21avery
requested review from
free6om,
heng4fun,
ldming,
leon-inf,
nayutah,
shanshanying and
wangyelei
as code owners
nayutah
previously approved these changes
Jan 25, 2024
shanshanying
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hello everyone, I have created a backup functionality following the documentation and relevant examples. I am using PostgreSQL's pg_basebackup feature to backup files. I have created two new files, one is backuppolicytemplate.yaml and the other is actionset-halobasebackup.yaml. Now my issue is that when I start the cluster, I do not see the related actions being created in the cron job. Can someone help me understand what could be the problem?