Merge pull request #5065 from hashicorp/clarify_separator_api
clarify how `separator` should be in CLI and API
This commit is contained in:
commit
7dfc32d1c4
|
@ -62,9 +62,10 @@ The table below shows this endpoint's support for
|
|||
metadata). Specifying this implies `recurse`. This is specified as part of the
|
||||
URL as a query parameter.
|
||||
|
||||
- `separator` `(string: '/')` - Specifies the character to use as a separator
|
||||
for recursive lookups. This is specified as part of the URL as a query
|
||||
parameter.
|
||||
- `separator` `(string: '/')` - Specifies the string to use as a separator
|
||||
for recursive key lookups. This option is only used when paired with the `keys`
|
||||
parameter to limit the prefix of keys returned, only up to the given separator.
|
||||
This is specified as part of the URL as a query parameter.
|
||||
|
||||
### Sample Request
|
||||
|
||||
|
|
|
@ -38,9 +38,9 @@ Usage: `consul kv get [options] [KEY_OR_PREFIX]`
|
|||
* `-recurse` - Recursively look at all keys prefixed with the given path. The
|
||||
default value is false.
|
||||
|
||||
* `-separator=<string>` - String to use as a separator between keys. The default
|
||||
value is "/", but this option is only taken into account when paired with the
|
||||
-keys flag.
|
||||
* `-separator=<string>` - String to use as a separator for recursive lookups. The
|
||||
default value is "/", and only used when paired with the `-keys` flag. This will
|
||||
limit the prefix of keys returned, only up to the given separator.
|
||||
|
||||
## Examples
|
||||
|
||||
|
|
Loading…
Reference in New Issue