From 38c2bf50db43476a2e1936f760ffe0c00b95c60b Mon Sep 17 00:00:00 2001 From: Nikolay Mikhaylichenko Date: Thu, 22 May 2025 06:41:14 +0300 Subject: [PATCH] Update operations-qs.mdx (#30573) Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- website/content/docs/get-started/operations-qs.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/docs/get-started/operations-qs.mdx b/website/content/docs/get-started/operations-qs.mdx index 1d48a23226..f9cc62c064 100644 --- a/website/content/docs/get-started/operations-qs.mdx +++ b/website/content/docs/get-started/operations-qs.mdx @@ -159,7 +159,7 @@ the operations allowed on plugin data. ```shell-session $ vault policy write kv-access-policy - << EOF - path "shared/data/kv/creds/*" { + path "shared/data/kv/creds" { capabilities = ["read", "create", "update", "delete"] } EOF @@ -187,7 +187,7 @@ the operations allowed on plugin data. 1. Try retrieving the secrets stored on the `kv/creds` path: ```shell-session - $ vault kv get kv/creds + $ vault kv get -mount=shared kv/creds ``` The command retrieves the secrets stored on the `kv/creds` path. @@ -195,11 +195,11 @@ the operations allowed on plugin data. 1. Try retrieving the secrets stored on the `kv/api-keys` path: ```shell-session - $ vault kv get kv/api-keys + $ vault kv get -mount=shared kv/api-keys ``` The second command fails because the policy for `opsuser` does not grant access to the `/api-keys` path. You have successfully stored and retrieved your first secret value with a user -from the `userpass` auth method. \ No newline at end of file +from the `userpass` auth method.