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

Signed-off-by: Adam Kupczyk <akupczyk@mirantis.com>

diff --git a/README.rst b/README.rst
index 0ce6584e010804b049b2ea2d516f0b953c7c2c0f..65294fafbf89ba8346e05b23bf0b40322540130f 100644 (file)
--- a/README.rst
+++ b/README.rst
@@ -56,6 +56,9 @@ service and two different credentials, something like this::
        access_key = ABCDEFGHIJKLMNOPQRST
        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]
        ## another user account, used for ACL-related tests
        user_id = 56789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234

diff --git a/config.yaml.SAMPLE b/config.yaml.SAMPLE
index 169acab436389e93a67db66493b56d293f983cb6..f18096e794ae1aa88f6988e679aa0a182ff3a2d5 100644 (file)
--- a/config.yaml.SAMPLE
+++ b/config.yaml.SAMPLE
@@ -71,6 +71,9 @@ s3:
     access_key: AWS_ACCESS_KEY
     secret_key: AWS_SECRET_KEY
 
+## If KMS is tested, this if barbican key id. Optional.
+   kms_keyid: barbican_key_id
+
   alt:
 ## Another user accout, used for ACL-related tests.