mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2025-11-13 14:51:34 +01:00
Code Issues Projects Releases Wiki Activity

Rewrite a confusing bit of policies docs re parameter constraints. (#16182)

Browse Source
This commit is contained in:
Nick Cabatoff 2022-06-29 12:28:49 -04:00 committed by GitHub
parent 7a79a8aac9
commit ed52771d63
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/docs/concepts/policies.mdx
View File

@ -340,10 +340,8 @@ path take precedence over permissions on parameters.
See the [API Specification](/api-docs/secret/kv/kv-v2) for more information.
In Vault, data is represented as `key=value` pairs. Vault policies can
optionally further restrict paths based on the keys and data at those keys when
evaluating the permissions for a path. The optional finer-grained control
options are:
Policies can take into account HTTP request parameters to further
constrain requests, using the following options:
- `required_parameters` - A list of parameters that must be specified.