From 17ed6663f7bee836c94d9cee4cd999863b30f14d Mon Sep 17 00:00:00 2001 From: Jim Kalafut Date: Wed, 14 Mar 2018 14:03:00 -0700 Subject: [PATCH] Fix description of parameter value globbing (#4131) --- website/source/docs/concepts/policies.html.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/website/source/docs/concepts/policies.html.md b/website/source/docs/concepts/policies.html.md index 6573db38dc..182af4a040 100644 --- a/website/source/docs/concepts/policies.html.md +++ b/website/source/docs/concepts/policies.html.md @@ -269,7 +269,7 @@ options are: ``` * If any keys are specified, all non-specified parameters will be denied - unless there the parameter `"*"` is set to an empty array, which will + unless the parameter `"*"` is set to an empty array, which will allow all other parameters to be modified. Parameters with specific values will still be restricted to those values. @@ -338,15 +338,18 @@ Parameter values also support prefix/suffix globbing. Globbing is enabled by prepending or appending or prepending a splat (`*`) to the value: ```ruby -# Allow any parameter as long as the value starts with "foo-*". +# Only allow a parameter named "bar" with a value starting with "foo-*". path "secret/foo" { capabilities = ["create"] allowed_parameters = { - "*" = ["foo-*"] + "bar" = ["foo-*"] } } ``` +Note: the only value that can be used with the `*` parameter is `[]`. + + ### Required Response Wrapping TTLs These parameters can be used to set minimums/maximums on TTLs set by clients