bc74650b98
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.
43 lines
1 KiB
Plaintext
43 lines
1 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: delete - Command
|
|
description: |-
|
|
The "delete" command deletes secrets and configuration from Vault at the given
|
|
path. The behavior of "delete" is delegated to the backend corresponding to
|
|
the given path.
|
|
---
|
|
|
|
# delete
|
|
|
|
The `delete` command deletes secrets and configuration from Vault at the given
|
|
path. The behavior of "delete" is delegated to the backend corresponding to the
|
|
given path.
|
|
|
|
## Examples
|
|
|
|
Remove data in the static secrets engine:
|
|
|
|
```shell-session
|
|
$ vault delete secret/my-secret
|
|
```
|
|
|
|
Uninstall an encryption key in the transit backend:
|
|
|
|
```shell-session
|
|
$ 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
|
|
$ vault delete aws/roles/ops
|
|
```
|
|
|
|
## Usage
|
|
|
|
There are no flags beyond the [standard set of flags](/docs/commands)
|
|
included on all commands.
|