summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2021-08-23 09:05:24 -0700
committerGitHub <noreply@github.com>2021-08-23 09:05:24 -0700
commit61b8cd3c68f4cace4d19fb2686379db3ebde009c (patch)
treecf148b9d94ee985578c565cc45cf81b1b2a59436
parent95b58f1daae9a8c9fad11ec196b7d3a8a5b8b38f (diff)
downloadchef-61b8cd3c68f4cace4d19fb2686379db3ebde009c.tar.gz
Update RELEASE_NOTES.md
Signed-off-by: Tim Smith <tsmith@chef.io> Co-authored-by: Kimberly Garmoe <kgarmoe@chef.io>
-rw-r--r--RELEASE_NOTES.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index a631b4dbb3..f426870e87 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -48,7 +48,7 @@ secret(name: "test-secret-1", service: :azure_key_vault, config: {vault: "test-c
#### AWS Default to Node's Region in AWS Secrets Manager
-When fetching secrets from AWS Secrets Manager the `secrets` helper will now default to fetching secrets from the region where the node resides. You can still specify the region if you'd like to fetch secrets from another region by passing the region config option:
+When fetching secrets from AWS Secrets Manager, the `secrets` helper now defaults to fetching secrets from the region where the node resides. If you need to fetch secrets from another region, you can use the region config option:
**Specifying AWS Region**