dkirillov/s3-tests
1
0
Fork 0
forked from TrueCloudLab/s3-tests
Code Pull requests Activity

Added micro instuction how to configure tests for KMS (barbican) integration

Browse source 
Signed-off-by: Adam Kupczyk <akupczyk@mirantis.com>
This commit is contained in:
Adam Kupczyk 2016-12-15 11:27:49 +01:00 committed by Casey Bodley
parent 05543b85b1
commit fa597a5bf1
2 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
README.rst
View file

@ -56,6 +56,9 @@ service and two different credentials, something like this::
access_key = ABCDEFGHIJKLMNOPQRST access_key = ABCDEFGHIJKLMNOPQRST
secret_key = abcdefghijklmnopqrstuvwxyzabcdefghijklmn secret_key = abcdefghijklmnopqrstuvwxyzabcdefghijklmn
## replace with key id obtained when secret is created, or delete if KMS not tested
kms_keyid = 01234567-89ab-cdef-0123-456789abcdef
[s3 alt] [s3 alt]
## another user account, used for ACL-related tests ## another user account, used for ACL-related tests
user_id = 56789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234 user_id = 56789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234

3
config.yaml.SAMPLE
View file

@ -71,6 +71,9 @@ s3:
access_key: AWS_ACCESS_KEY access_key: AWS_ACCESS_KEY
secret_key: AWS_SECRET_KEY secret_key: AWS_SECRET_KEY
## If KMS is tested, this if barbican key id. Optional.
kms_keyid: barbican_key_id
alt: alt:
## Another user accout, used for ACL-related tests. ## Another user accout, used for ACL-related tests.