Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Feature/custom restore data dir #638
Conversation
making sure that the feature is disabled by default
|
@maclarel thanks for the feedback ...I'll address the merge conflict and we should be good to go for another |
This provides an option for the backup/restore utilities to use separate base directories
Based on a customer use case:
This feature provides an option for the backup/restore utilities to use separate base directories. It introduces GHE_RESTORE_DATA_DIR.
Allowing users to restore from a different data location, then the backup.
All original Backup/Restore functionality (cmd options) remain the same, this simply adds additional flexibility. If no
GHE_RESTORE_DATA_DIRis provided in thebackup.configfile, the originalGHE_DATA_DIRwill be used.This was "life" tested with the GitHub-Demo-Stack (AWS) and an additional EC2 Restore Instance
Note:
To address the customer's use case, alternative solutions, that don't require a code change, could have been used.
For example, run " a different backup-utils installation" (for restore actions), or don't back up and delete the whole backup folder, only individual snapshots, etc.
The decision to add more flexibility to our tools comes from the fact that this would not require the customer(s) to adjust their process (or policy) and that this adds additional flexibility without interfering with the existing functionality.
Test Runs
/cc @michaelsainz @steffen