feat(backup): validate extra_volumes paths during database creation and update#44
Merged
tsivaprasad merged 6 commits intomainfrom Jun 9, 2025
Conversation
…fy that specified extra_volumes paths exist and are accessible
jason-lynch
reviewed
Jun 6, 2025
jason-lynch
reviewed
Jun 9, 2025
jason-lynch
reviewed
Jun 9, 2025
jason-lynch
reviewed
Jun 9, 2025
jason-lynch
approved these changes
Jun 9, 2025
Member
jason-lynch
left a comment
There was a problem hiding this comment.
Functionality looks good! Just left two minor suggestions for the output types. It's important to have separate types because these get written to/read from storage, and workflows can be interrupted and resumed (and maybe retried in the future). Once this is in production, there are some extra edge cases to consider when we modify the inputs and outputs. Having separate types doesn't remove those edge cases, but it limits the impact and makes it easier to understand the scope of a change if we need to change the inputs and outputs later on.
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
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.
This PR adds validation of
extra_volumespaths during database creation and update to ensure all specified mount points exist and are accessible on the host system. It improves reliability by preventing invalid volume configurations early in the workflow.Validation
Cluster Setup:
Created a 3-node cluster.
Initialized nodes to join the same cluster environment using:
Create Database Validation:
Backup database:
restish control-plane-local-1 backup-database-node f2f1cae9-6f37-4609-aa98-d0991bff3493 n1 '{ "type": "full" }'
Create New Database with Backup Restore:
Similar error as create database invalid input with bind mount failure.
Database created successfully with restore configuration using mounted volumes.
Update Database Validation:
restish control-plane-local-1 update-database f2f1cae9-6f37-4609-aa98-d0991bff3494 <update.json
Valid Input Example:
restish control-plane-local-1 list-databases
PLAT-94