From 7ab969fdfb559c82712085b176ee0b4a953a236b Mon Sep 17 00:00:00 2001 From: rgee0 Date: Thu, 12 Apr 2018 20:44:32 +0100 Subject: [PATCH] Fix apikey-secret README.md Following the existing README instructions would result in an error when the user attempted to create the secret. This small change remediates the instruction so that the secret is successfully created. Signed-off-by: rgee0 --- sample-functions/apikey-secret/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sample-functions/apikey-secret/README.md b/sample-functions/apikey-secret/README.md index 32c8d8dc..d862c950 100644 --- a/sample-functions/apikey-secret/README.md +++ b/sample-functions/apikey-secret/README.md @@ -2,7 +2,7 @@ This function returns access denied, or unlocked depending on whether your header for X-Api-Key matches a secret in the cluster called `secret_api_key`. -See the [secure secret management guide](../guide/secure_secret_management.md) for more information on secrets. +See the [secure secret management guide](../../guide/secure_secret_management.md) for more information on secrets. ## Trying the sample: @@ -11,7 +11,7 @@ See the [secure secret management guide](../guide/secure_secret_management.md) f $ docker secret remove secret_api_key # make sure we delete any existing secret # Create a secret with Swarm -$ echo "secret_value_goes_here" | docker secret create secret_api_key +$ echo -n "secret_value_goes_here" | docker secret create secret_api_key - # Deploy this sample with Docker Swarm and attach the secret to it