change indentation level of cas field (#18806)

* change indentation leve of cas field

* change formatting for cas_required

Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>

Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>
This commit is contained in:
Chris Capurso
2023-01-24 15:27:15 -05:00
committed by GitHub
parent 4a98e44533
commit 8f3dc3082c

View File

@@ -153,11 +153,11 @@ have an ACL policy granting the `update` capability.
- `options` `(Map: <optional>)` An object that holds option settings.
- `cas` `(int: <optional>)` - This flag is required if cas_required is set
- `cas` `(int: <optional>)` - This flag is required if `cas_required` is set
to true on either the secret or the engine's config. If not set the write
will be allowed. In order for a write to be successful, `cas` must be set to
the current version of the secret. If set to 0 a write will only be allowed if
the key doesnt exist as unset keys do not have any version information. Also
the key doesn't exist as unset keys do not have any version information. Also
remember that soft deletes do not remove any underlying version data from storage.
In order to write to a soft deleted key, the cas parameter must match the key's
current version.
@@ -224,7 +224,7 @@ applying a patch with the provided data.
- `options` `(Map: <optional>)` An object that holds option settings.
- `cas` `(int: <optional>)` - This flag is required if `cas_required` is set to true on either
- `cas` `(int: <optional>)` - This flag is required if `cas_required` is set to true on either
the secret or the engine's config. In order for a write to be successful, `cas` must be set
to the current version of the secret. A patch operation must be attempted on an existing
key, thus the provided `cas` value must be greater than 0.