This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
test: run e2e test pod without framework setup #318
Conversation
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
fanminshi
reviewed
May 24, 2018
test/e2e/backup_restore_test.go
Outdated
| func TestBackupRestoreOnVault(t *testing.T) { | ||
|
|
|
lgtm after nits. |
hasbro17
force-pushed
the
haseeb/ra-test-pod
branch
from
7916621
to
5d7b5cb
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Added a simplified version of the current test/pod that allows the e2e tests to be run against an existing vault and etcd operator setup.
The multistage Dockerfile builds the test binary separately to reduce the final test-container image size.
Additionally the backup and restore tests are skipped if the S3 bucket and AWS secret env are not set.
/cc @fanminshi @colhom