luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

docs: Fix small errors for node identities and acl-rules (#13016) 

* Fix node identities `datacenter` description to string type
* Fix service rules URL anchor
This commit is contained in:
Robert 2022-05-10 20:14:21 -05:00 committed by GitHub
parent c855df87ec
commit 4bc4f8773d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/docs/security/acl/acl-roles.mdx
View File

@ -260,7 +260,7 @@ Use the following syntax to define a node identity:
"NodeIdentities": [
{
"NodeName": "<node name>",
"Datacenters": ["<datacenter name>"]
"Datacenter": "<datacenter name>"
}
]
}
@ -270,7 +270,7 @@ Use the following syntax to define a node identity:
```hcl
NodeIdentities = {
NodeName = "<node name>"
Datacenters = ["<datacenter name>"]
Datacenter = "<datacenter name>"
}
```
@ -278,7 +278,7 @@ NodeIdentities = {
- `NodeIdentities`: Declares a node identity block.
- `NodeIdentities.NodeName`: String value that specifies the name of the node you want to associate with the policy.
- `NodeIdentities.Datacenters`: Array that specifies the names of datacenters in which the node identity applies. This field is optional.
- `NodeIdentities.Datacenter`: String value that specifies the name of the datacenter in which the node identity applies.
Refer to the the [API documentation for roles](/api-docs/acl/roles#sample-payload) for additional information and examples.

2
website/content/docs/security/acl/acl-rules.mdx
View File

@ -26,7 +26,7 @@ The following table provides an overview of the resources you can use to create
| `node`<br/>`node_prefix` &nbsp; | Controls access to node-level operations in the [Catalog API](/api-docs/catalog), [Health API](/api-docs/health), [Prepared Query API](/api-docs/query), [Network Coordinate API](/api-docs/coordinate), and [Agent API](/api-docs/agent) <br/>See [Node Rules](#node-rules) for details. | Yes |
| `operator` &nbsp; &nbsp; &nbsp; | Controls access to cluster-level operations available in the [Operator API](/api-docs/operator) excluding keyring API endpoints. <br/>See [Operator Rules](#operator-rules) for details. | No |
| `query`<br/>`query_prefix` | Controls access to create, update, and delete prepared queries in the [Prepared Query API](/api-docs/query). Access to the [node](#node-rules) and [service](#service-rules) must also be granted. <br/>See [Prepared Query Rules](#prepared-query-rules) for details. | Yes |
| `service`<br/>`service_prefix` | Controls service-level operations in the [Catalog API](/api-docs/catalog), [Health API](/api-docs/health), [Intentions API](/api-docs/connect/intentions), [Prepared Query API](/api-docs/query), and [Agent API](/api-docs/agent). <br/>See [Service Rules](#node-rules) for details. | Yes |
| `service`<br/>`service_prefix` | Controls service-level operations in the [Catalog API](/api-docs/catalog), [Health API](/api-docs/health), [Intentions API](/api-docs/connect/intentions), [Prepared Query API](/api-docs/query), and [Agent API](/api-docs/agent). <br/>See [Service Rules](#service-rules) for details. | Yes |
| `session`<br/>`session_prefix` | Controls access to operations in the [Session API](/api-docs/session). <br/>See [Session Rules](#session-rules) for details. | Yes |
The following resources are not covered by ACL policies: