Merged
Conversation
To hide the settings backups and to make the backup name copy/pasteable
viliakov
approved these changes
Apr 8, 2026
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
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.
The
sts-backup settingsandsts-backup stackgraphcommands both automatically restore the related stackgraph backups but--skip-stackpackscan be used to not restore those. Typically a user will want to restore also the stackpacks to get a fully consistent state.StackPack backups are implemented with a separate backup file and need to be restored using a dedicated command, but the
sts-backupcli takes care of that. The backup creation takes care of creating the stackpacks backup together with the settings and stackgraph backups such that the result will be a consistent backup set.