You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As defined in the vault API documentation, I would like to be able to specify the following fields on a vault_mount resource.
audit_non_hmac_request_keys(array: []) - Specifies the comma-separated list of keys that will not be HMAC'd by audit devices in the request data object.
audit_non_hmac_response_keys(array: []) - Specifies the comma-separated list of keys that will not be HMAC'd by audit devices in the response data object.
I am also blocked by lack of full support of the API on the vault_mount resource. I am unable to work around it with vault_generic_endpoint, and the generic options parameter is not applicable. For comparison, vault_auth_backend implements all parameters. This resource should do the same.
It's been over 1.5 years since this was reported. I started to prepare a patch to add support, but other priorities have prevailed. Any other progress?
As defined in the vault API documentation, I would like to be able to specify the following fields on a
vault_mount
resource.audit_non_hmac_request_keys
(array: [])
- Specifies the comma-separated list of keys that will not be HMAC'd by audit devices in the request data object.audit_non_hmac_response_keys
(array: [])
- Specifies the comma-separated list of keys that will not be HMAC'd by audit devices in the response data object.https://www.vaultproject.io/api-docs/system/mounts/#tune-mount-configuration
The text was updated successfully, but these errors were encountered: