summaryrefslogtreecommitdiff
path: root/RELEASE_NOTES.md
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2021-08-23 14:19:47 -0700
committerGitHub <noreply@github.com>2021-08-23 14:19:47 -0700
commit0ea9ed7f6a93815f3f30e8b83dd3512c7a765b40 (patch)
tree58c8ddb18f1bb076519e26a387582ccc1331a026 /RELEASE_NOTES.md
parent68acd9d44eab0dd3b7674eafebee6a0d934c8298 (diff)
downloadchef-0ea9ed7f6a93815f3f30e8b83dd3512c7a765b40.tar.gz
Update RELEASE_NOTES.md
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r--RELEASE_NOTES.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index cc40fd4930..1ee6d8f9c7 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -34,13 +34,13 @@ We've updated our beta secrets management integration helper to improve the expe
The `secrets` helper has been updated to allow specifying the Azure Key Vault to fetch a secret using the name instead of the config hash:
-**Specifying the Vault in the Name**
+Specifying the Vault in the Name:
```ruby
secret(name: "test-chef-infra-secrets/test-secret-1", service: :azure_key_vault)
```
-**Specifying the Vault in the Options Hash**
+Specifying the Vault in the Options Hash:
```ruby
secret(name: "test-secret-1", service: :azure_key_vault, config: {vault: "test-chef-infra-secrets" })
@@ -50,13 +50,13 @@ secret(name: "test-secret-1", service: :azure_key_vault, config: {vault: "test-c
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**
+Specifying AWS Region:
```ruby
secret(name: 'test1', service: :aws_secrets_manager, config: { region: 'us-west-2' })
```
-**Using the Node's Region**
+Using the Node's Region:
```ruby
secret(name: 'test1', service: :aws_secrets_manager)