From 3f66120d6325a5e058780dbf531a974cde57de5e Mon Sep 17 00:00:00 2001 From: greenie-msft <56556602+greenie-msft@users.noreply.github.com> Date: Thu, 2 Dec 2021 13:43:12 -0800 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/secrets/howto-secrets.md --- .../building-blocks/secrets/howto-secrets.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/secrets/howto-secrets.md b/daprdocs/content/en/developing-applications/building-blocks/secrets/howto-secrets.md index 3ecb2c9a3..73565e055 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/secrets/howto-secrets.md +++ b/daprdocs/content/en/developing-applications/building-blocks/secrets/howto-secrets.md @@ -18,7 +18,9 @@ The below code example loosely describes an application that processes orders. I Before retrieving secrets in your application's code, you must have a secret store component configured. For the purposes of this guide, as an example you will configure a local secret store which uses a local JSON file to store secrets. ->Note: In a production-grade application, local secret stores are not recommended. You can find other alternatives [here]({{}}) to securely manage your secrets. +{{% alert title="Warning" color="warning" %}} +In a production-grade application, local secret stores are not recommended. You can find other alternatives [here]({{}}) to securely manage your secrets. +{{% /alert %}} Create a file named `secrets.json` with the following contents: