Document the deletion_allowed transform flag (#17544)

* Document the deletion_allowed transform flag

* Remove duplicated sentence
This commit is contained in:
Scott Miller 2022-10-13 16:31:07 -05:00 committed by GitHub
parent 7c974beee4
commit b5047fd8c8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -181,7 +181,9 @@ configuration endpoints, and will be removed in a future release.
A role using this transformation must exist in this list in order for
encode and decode operations to properly function.
-
- `deletion_allowed` `(bool: false)` -
If true, this transform can be deleted. Otherwise deletion is blocked while
this value remains false.
### Sample Payload
@ -233,6 +235,12 @@ transformation exists, it will be updated with the new attributes.
A role using this transformation must exist in this list in order for
encode and decode operations to properly function.
- `deletion_allowed` `(bool: false)` -
If true, this transform can be deleted. Otherwise deletion is blocked while this
value remains false. Note that deleting the transform deletes the underlying
key making decoding of FPE encoded values impossible without restoring from a
backup.
### Sample Payload
```json
@ -337,6 +345,11 @@ transformation exists, it will be updated with the new attributes.
The list of tokenization stores to use for tokenization state. Vault's
internal storage is used by default.
- `deletion_allowed` `(bool: false)` -
If true, this transform can be deleted. Otherwise deletion is blocked while this
value remains false. Note that deleting the transform deletes the underlying key
making decoding of tokenized values impossible without restoring from a backup.
### Sample Payload
```json