luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

docs: fix consul secrets feature version (#16304) 

* Move consul_namespace into Consul v1.7 instead of v1.8
This commit is contained in:
Robert 2022-07-18 13:03:45 -05:00 committed by GitHub
parent 12e7c4553c
commit 8169940284
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
website/content/api-docs/secret/consul.mdx
View File

@ -80,9 +80,9 @@ Consul version.
### Parameters for Consul versions 1.11 and above
- `partition` `(string: "default")` - Specifies the Consul admin partition in which the token is generated.
- `partition` `(string: "")` - Specifies the Consul admin partition in which the token is generated.
The partition must exist, and the Consul policies or roles assigned to the
Vault role must also exist inside the given partition. If it's not provided, the partition `default`
Vault role must also exist inside the given partition. If not provided, the partition `default`
is used.
To create a client token within a particular Consul admin partition:
@ -95,22 +95,9 @@ To create a client token within a particular Consul admin partition:
### Parameters for Consul versions 1.8 and above
- `consul_namespace` `(string: "default")` - Specifies the Consul namespace in which the token is generated.
The namespace must exist, and the Consul policies or roles assigned
to the Vault role must also exist inside the given Consul namespace. If not provided, the
namespace `default` is used.
- `node_identities` `(list: <node identity or identities>)` - The list of node identities to assign to the generated
token. This may be a comma-separated list to attach multiple node identities to a token.
To create a client token within a particular Consul namespace:
```json
{
"consul_namespace": "ns1"
}
```
To create a client token with node identities attached:
```json
@ -122,6 +109,20 @@ To create a client token with node identities attached:
}
```
### Parameters for Consul versions 1.7 and above
- `consul_namespace` `(string: "")` - Specifies the Consul namespace in which the token is generated.
The namespace must exist, and the Consul policies or roles assigned to the Vault role must also exist
inside the given Consul namespace. If not provided, the namespace `default` is used.
To create a client token within a particular Consul namespace:
```json
{
"consul_namespace": "ns1"
}
```
### Parameters for Consul version 1.5 and above
- `service_identities` `(list: <service identity or identities>)` - The list of service identities to assign to the generated