This repository has been archived by the owner on Nov 20, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 57
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added integration tests for Aws::S3::Encryption::Client.
- Loading branch information
1 parent
5b58955
commit a056f35
Showing
2 changed files
with
66 additions
and
0 deletions.
There are no files selected for viewing
21 changes: 21 additions & 0 deletions
21
aws-sdk-resources/features/s3/client_side_encryption.feature
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,21 @@ | ||
# language: en | ||
@s3 @client-side-encryption | ||
Feature: S3 Objects | ||
|
||
Background: | ||
Given I create a bucket | ||
|
||
Scenario: Encrypting client-side with GET and PUT | ||
Given I have an encryption client | ||
When I perform an encrypted PUT of the value "secret" | ||
And I GET the object with a non-encyrption client | ||
Then the object data should be encrypted | ||
When I GET the object with an encryption client | ||
Then the object data should be "secret" | ||
|
||
Scenario: Using instruction file for storing the encryption envelope | ||
Given I have an encryption client configured for :instruction_file | ||
When I perform an encrypted PUT of the value "secret" | ||
Then the instruction file should exist | ||
When I GET the object with an encryption client | ||
Then the object data should be "secret" |
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
a056f35
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.
Isn't this supposed to be
@plain_text
? (Apologies for pedantry if not)a056f35
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.
@skyhighwings Can you clarify what line you are referencing?
a056f35
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.
@skyhighwings If you are referencing line 65, then no. This line is using a vanilla, non-encryption client to get the encrypted data, e.g. the cipher text.
a056f35
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.
@trevorrowe
Nope, line 69!
+ expect(@cipher_text).not_to eq(@plaint_text)
.I feel like I clicked on that and GitHub somehow failed to attach it to the correct line number.