Add backup/restore integration tests #2012
There are no files selected for viewing
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| #!/usr/bin/env bash | ||
| set -ex | ||
|
|
||
| source install/_lib.sh | ||
| source install/dc-detect-version.sh | ||
|
|
||
| echo "${_group}Test that backup/restore works..." | ||
| echo "Creating backup..." | ||
| backup_path="$(pwd)/sentry/backup" | ||
| mkdir -p $backup_path | ||
| # Docker was giving me permissioning issues when trying to create this file and write to it even after giving read + write access | ||
| # to group and owner. Instead, try creating the empty file and then give everyone write access to the backup file | ||
| touch $backup_path/backup.json | ||
| chmod 666 $backup_path/backup.json | ||
| $dcr -v $backup_path:/sentry-data/backup -T -e SENTRY_LOG_LEVEL=CRITICAL web export /sentry-data/backup/backup.json | ||
| # check to make sure there is content in the file | ||
| if [ ! -s "$backup_path/backup.json" ]; then | ||
| echo "Backup file is empty" | ||
| exit 1 | ||
| fi | ||
|
|
||
| # bring postgres down and recreate the docker volume | ||
| $dc stop postgres | ||
| sleep 5 | ||
| $dc rm -f -v postgres | ||
| docker volume rm sentry-postgres | ||
| export SKIP_USER_CREATION=1 | ||
| source install/create-docker-volumes.sh | ||
| source install/set-up-and-migrate-database.sh | ||
| $dc up -d | ||
|
|
||
| # echo "Importing backup..." | ||
|
|
||
| $dcr --rm -T web import /etc/sentry/backup/backup.json | ||
|
There was a problem hiding this comment. This matches the docs basically. Fine to use $dcr I guess vs. writing it out (like in the docs) if $dcr is necessary to get the test infra to work. There was a problem hiding this comment. it's not necessary to get it to work, For this use case I can use the exact command the docs is using |
||
|
|
||
| rm $(pwd)/sentry/backup/backup.json | ||
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,6 +10,7 @@ echo "Testing initial install" | |
| ./install.sh | ||
| _integration-test/run.sh | ||
| _integration-test/ensure-customizations-not-present.sh | ||
| _integration-test/ensure-backup-restore-works.sh | ||
|
|
||
| echo "Make customizations" | ||
| cat <<EOT >sentry/enhance-image.sh | ||
|
|
@@ -25,3 +26,4 @@ echo "Testing in-place upgrade and customizations" | |
| ./install.sh --minimize-downtime | ||
| _integration-test/run.sh | ||
| _integration-test/ensure-customizations-work.sh | ||
| _integration-test/ensure-backup-restore-works.sh | ||
|
There was a problem hiding this comment. A little goofy that we have to call this twice, but I guess that's where we're at and we clean up the test suite under getsentry/team-ospo#91. |
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would love to see this match the docs exactly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With a comment saying as much.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you can't get it exactly like the docs that's fine, just say so in the comment.