From 4bc4f8773dd886fecf6bc578affe7b5871bf67ba Mon Sep 17 00:00:00 2001 From: Robert <17119716+robmonte@users.noreply.github.com> Date: Tue, 10 May 2022 20:14:21 -0500 Subject: [PATCH] docs: Fix small errors for node identities and acl-rules (#13016) * Fix node identities `datacenter` description to string type * Fix service rules URL anchor --- website/content/docs/security/acl/acl-roles.mdx | 6 +++--- website/content/docs/security/acl/acl-rules.mdx | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/docs/security/acl/acl-roles.mdx b/website/content/docs/security/acl/acl-roles.mdx index 27fc221f6..1421472c1 100644 --- a/website/content/docs/security/acl/acl-roles.mdx +++ b/website/content/docs/security/acl/acl-roles.mdx @@ -260,7 +260,7 @@ Use the following syntax to define a node identity: "NodeIdentities": [ { "NodeName": "", - "Datacenters": [""] + "Datacenter": "" } ] } @@ -270,7 +270,7 @@ Use the following syntax to define a node identity: ```hcl NodeIdentities = { NodeName = "" - Datacenters = [""] + Datacenter = "" } ``` @@ -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. diff --git a/website/content/docs/security/acl/acl-rules.mdx b/website/content/docs/security/acl/acl-rules.mdx index 5e6762c74..a5941d6f7 100644 --- a/website/content/docs/security/acl/acl-rules.mdx +++ b/website/content/docs/security/acl/acl-rules.mdx @@ -26,7 +26,7 @@ The following table provides an overview of the resources you can use to create | `node`
`node_prefix`   | 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)
See [Node Rules](#node-rules) for details. | Yes | | `operator`       | Controls access to cluster-level operations available in the [Operator API](/api-docs/operator) excluding keyring API endpoints.
See [Operator Rules](#operator-rules) for details. | No | | `query`
`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.
See [Prepared Query Rules](#prepared-query-rules) for details. | Yes | -| `service`
`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).
See [Service Rules](#node-rules) for details. | Yes | +| `service`
`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).
See [Service Rules](#service-rules) for details. | Yes | | `session`
`session_prefix` | Controls access to operations in the [Session API](/api-docs/session).
See [Session Rules](#session-rules) for details. | Yes | The following resources are not covered by ACL policies: