CHORE: update kvv2 patch docs to clarify behavior when secret does not exist (#1008)

swayne275 · schavis · web-flow · commit 1aa53f2ed5d4 · 2025-10-01T22:44:56.000Z
* add clarity around kvv2 patch * Apply suggestion from @schavis Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> * Apply suggestion from @schavis Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> * fix issues from accepting suggestions? * Apply suggestion from @schavis --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
diff --git a/content/vault/v1.20.x/content/docs/secrets/kv/kv-v2/cookbook/patch-data.mdx b/content/vault/v1.20.x/content/docs/secrets/kv/kv-v2/cookbook/patch-data.mdx
@@ -12,13 +12,15 @@ an existing data path in the `kv` v2 plugin.
 
 <Tip title="Assumptions">
 
-- You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). 
+- You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup).
 - Your authentication token has appropriate permissions for the `kv` v2 plugin:
    - **`patch`** permission to make direct updates with `PATCH` actions.
    - **`create`**+**`update`** permission if you want to make indirect
       updates with the Vault CLI by combining `GET` and `POST` actions.
 - You know the keys or [subkeys](/vault/docs/secrets/kv/kv-v2/cookbook/read-subkey)
   you want to patch.
+- The secret path you want to update already exists. You cannot create
+  new paths with a patch.
 
 </Tip>
 
