From fa597a5bf16322ab71662b4cb38ebec2cf508631 Mon Sep 17 00:00:00 2001
From: Adam Kupczyk <akupczyk@mirantis.com>
Date: Thu, 15 Dec 2016 11:27:49 +0100
Subject: [PATCH] Added micro instuction how to configure tests for KMS
 (barbican) integration

Signed-off-by: Adam Kupczyk <akupczyk@mirantis.com>
---
 README.rst         | 3 +++
 config.yaml.SAMPLE | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/README.rst b/README.rst
index 0ce6584..65294fa 100644
--- 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 169acab..f18096e 100644
--- 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.