From d2bb013653b5353a2a9f47b88116f89cc826f2fc Mon Sep 17 00:00:00 2001 From: mairandomness Date: Fri, 4 Feb 2022 10:13:24 -0800 Subject: [PATCH] Update delete.mdx (#13148) Adding a note on the parameter necessary for deletion on a key deletion example seems like a good idea. From my limited research I found other people that had trouble finding the relevant part of the documentation. Though I'm not sure this is the best wording or formatting for it. --- website/content/docs/commands/delete.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/website/content/docs/commands/delete.mdx b/website/content/docs/commands/delete.mdx index 9007034fb4..5f1326906c 100644 --- a/website/content/docs/commands/delete.mdx +++ b/website/content/docs/commands/delete.mdx @@ -27,6 +27,9 @@ Uninstall an encryption key in the transit backend: $ vault delete transit/keys/my-key ``` +Note: changing the `deletion_allowed` parameter to `true` is necessary for the +key to be successfully deleted, you can read more on key parameters [here](/api/secret/transit#update-key-configuration) + Delete an IAM role: ```shell-session