adding AWS - database backup/restore #18
Open
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 Problem/Issue/Bug
It's not possible to maintain consistent database across workspaces.
How this PR Solves The Problem
Add AWS commands:
.gitpod/aws/aws-backup.sh [backup_name]
.gitpod/aws/aws-restore.sh [backup_name]
Manual Testing Instructions
gp env AWS_ACCESS_KEY_ID=[ID]
gp env AWS_SECRET_ACCESS_KEY=[SECRET]
gp env AWS_DEFAULT_BUCKET=[BUCKET_NAME]
gp env
to take effect)aws-backup.sh testing123
(for a named backup)aws-backup.sh
(for general backup, to be used later in Gitpod's future end-tasks)aws-restore.sh testing123
(for restoring the named backup)aws-restore.sh
(for restoring the latest backup available)Related Issue Link(s)
Release/Deployment notes