Fixed absolute links to HTTP apis.

2022-01-11 08:26:58 -05:00 · 2022-01-11 08:26:58 -05:00 · 079f27ee52
parent dcdaefcf79
commit 079f27ee52
72 changed files with 83 additions and 83 deletions
--- a/website/content/commands/acl/auth-method/create.mdx
+++ b/website/content/commands/acl/auth-method/create.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Auth Method Create'

 Command: `consul acl auth-method create`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/auth-method](https://www.consul.io/api-docs/acl/auth-methods#create-an-auth-method)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/auth-method](/api-docs/acl/auth-methods#create-an-auth-method)

 The `acl auth-method create` command creates new auth methods.

--- a/website/content/commands/acl/auth-method/delete.mdx
+++ b/website/content/commands/acl/auth-method/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Auth Method Delete'

 Command: `consul acl auth-method delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/auth-method/:name](https://www.consul.io/api-docs/acl/auth-methods#delete-an-auth-method)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/auth-method/:name](/api-docs/acl/auth-methods#delete-an-auth-method)

 The `acl auth-method delete` command deletes an auth method.

--- a/website/content/commands/acl/auth-method/list.mdx
+++ b/website/content/commands/acl/auth-method/list.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Auth Method List'

 Command: `consul acl auth-method list`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/auth-methods](https://www.consul.io/api-docs/acl/auth-methods#list-auth-methods)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/auth-methods](/api-docs/acl/auth-methods#list-auth-methods)

 The `acl auth-method list` command lists all auth methods. By default it will not show metadata.

--- a/website/content/commands/acl/auth-method/read.mdx
+++ b/website/content/commands/acl/auth-method/read.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Auth Method Read'

 Command: `consul acl auth-method read`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/auth-method/:name](https://www.consul.io/api-docs/acl/auth-methods#read-an-auth-method)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/auth-method/:name](/api-docs/acl/auth-methods#read-an-auth-method)

 The `acl auth-method read` command reads and displays an auth method's details.

--- a/website/content/commands/acl/auth-method/update.mdx
+++ b/website/content/commands/acl/auth-method/update.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Auth Method Update'

 Command: `consul acl auth-method update`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/auth-method/:name](https://www.consul.io/api-docs/acl/auth-methods#update-an-auth-method)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/auth-method/:name](/api-docs/acl/auth-methods#update-an-auth-method)

 The `acl auth-method update` command is used to update an auth method. The
 default operations is to merge the current auth method with those values
--- a/website/content/commands/acl/binding-rule/create.mdx
+++ b/website/content/commands/acl/binding-rule/create.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Binding Rule Create'

 Command: `consul acl binding-rule create`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/binding-rule](https://www.consul.io/api-docs/acl/binding-rules#create-a-binding-rule)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/binding-rule](/api-docs/acl/binding-rules#create-a-binding-rule)

 The `acl binding-rule create` command creates new binding rules.

--- a/website/content/commands/acl/binding-rule/delete.mdx
+++ b/website/content/commands/acl/binding-rule/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Binding Rule Delete'

 Command: `consul acl binding-rule delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/binding-rule/:id](https://www.consul.io/api-docs/acl/binding-rules#delete-a-binding-rule)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/binding-rule/:id](/api-docs/acl/binding-rules#delete-a-binding-rule)

 The `acl binding-rule delete` command deletes a binding rule.

--- a/website/content/commands/acl/binding-rule/list.mdx
+++ b/website/content/commands/acl/binding-rule/list.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Binding Rule List'

 Command: `consul acl binding-rule list`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/binding-rules](https://www.consul.io/api-docs/acl/binding-rules#list-binding-rules)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/binding-rules](/api-docs/acl/binding-rules#list-binding-rules)

 The `acl binding-rule list` command lists all binding rules. By default it will not show metadata.

--- a/website/content/commands/acl/binding-rule/read.mdx
+++ b/website/content/commands/acl/binding-rule/read.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Binding Rule Read'

 Command: `consul acl binding-rule read`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/binding-rule/:id](https://www.consul.io/api-docs/acl/binding-rules#read-a-binding-rule)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/binding-rule/:id](/api-docs/acl/binding-rules#read-a-binding-rule)

 The `acl binding-rule read` command reads and displays a binding rules details.

--- a/website/content/commands/acl/binding-rule/update.mdx
+++ b/website/content/commands/acl/binding-rule/update.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Binding Rule Update'

 Command: `consul acl binding-rule update`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/binding-rule/:id](https://www.consul.io/api-docs/acl/binding-rules#update-a-binding-rule)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/binding-rule/:id](/api-docs/acl/binding-rules#update-a-binding-rule)

 The `acl binding-rule update` command is used to update a binding rule. The
 default operations is to merge the current binding rule with those values
--- a/website/content/commands/acl/bootstrap.mdx
+++ b/website/content/commands/acl/bootstrap.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Bootstrap'

 Command: `consul acl bootstrap`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/bootstrap](https://www.consul.io/api-docs/acl#bootstrap-acls)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/bootstrap](/api-docs/acl#bootstrap-acls)

 The `acl bootstrap` command will request Consul to generate a new token with unlimited privileges to use
 for management purposes and output its details. This can only be done once and afterwards bootstrapping
--- a/website/content/commands/acl/policy/create.mdx
+++ b/website/content/commands/acl/policy/create.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Policy Create'

 Command: `consul acl policy create`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/policy](https://www.consul.io/api-docs/acl/policies#create-a-policy)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/policy](/api-docs/acl/policies#create-a-policy)

 The `acl policy create` command creates new policies. The policies rules can either be set explicitly or the
 `-from-token` parameter may be used to load the rules from a legacy ACL token. When loading
--- a/website/content/commands/acl/policy/delete.mdx
+++ b/website/content/commands/acl/policy/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Policy Delete'

 Command: `consul acl policy delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/policy/:id](https://www.consul.io/api-docs/acl/policies#delete-a-policy)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/policy/:id](/api-docs/acl/policies#delete-a-policy)

 The `acl policy delete` command deletes a policy. Policies may be deleted by their ID or by name.

--- a/website/content/commands/acl/policy/list.mdx
+++ b/website/content/commands/acl/policy/list.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Policy List'

 Command: `consul acl policy list`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/policies](https://www.consul.io/api-docs/acl/policies#list-policies)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/policies](/api-docs/acl/policies#list-policies)

 The `acl policy list` command lists all policies. By default it will not show metadata.

--- a/website/content/commands/acl/policy/read.mdx
+++ b/website/content/commands/acl/policy/read.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Policy Read'

 Command: `consul acl policy read`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/policy/:id](https://www.consul.io/api-docs/acl/policies#read-a-policy)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/policy/:id](/api-docs/acl/policies#read-a-policy)

 The `acl policy read` command reads and displays a policies details.

--- a/website/content/commands/acl/policy/update.mdx
+++ b/website/content/commands/acl/policy/update.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Policy Update'

 Command: `consul acl policy update`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/policy/:id](https://www.consul.io/api-docs/acl/policies#update-a-policy)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/policy/:id](/api-docs/acl/policies#update-a-policy)

 The `acl policy update` command is used to update a policy. The default operations is to merge the current policy
 with those values provided to the command invocation. Therefore to update just one field, only
--- a/website/content/commands/acl/role/create.mdx
+++ b/website/content/commands/acl/role/create.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Role Create'

 Command: `consul acl role create`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/role](https://www.consul.io/api-docs/acl/roles#create-a-role)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/role](/api-docs/acl/roles#create-a-role)

 The `acl role create` command creates new roles.

--- a/website/content/commands/acl/role/delete.mdx
+++ b/website/content/commands/acl/role/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Role Delete'

 Command: `consul acl role delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/role/:id](https://www.consul.io/api-docs/acl/roles#delete-a-role)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/role/:id](/api-docs/acl/roles#delete-a-role)

 The `acl role delete` command deletes a role. Roles may be deleted by their ID or by name.

--- a/website/content/commands/acl/role/list.mdx
+++ b/website/content/commands/acl/role/list.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Role List'

 Command: `consul acl role list`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/roles](https://www.consul.io/api-docs/acl/roles#list-roles)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/roles](/api-docs/acl/roles#list-roles)

 The `acl role list` command lists all roles. By default it will not show metadata.

--- a/website/content/commands/acl/role/read.mdx
+++ b/website/content/commands/acl/role/read.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Role Read'

 Command: `consul acl role read`

-Corresponding HTTP API Endpoints: [\[GET\] /v1/acl/role/:id](https://www.consul.io/api-docs/acl/roles#read-a-role), [\[GET\] /v1/acl/role/name/:name](https://www.consul.io/api-docs/acl/roles#read-a-role-by-name)
+Corresponding HTTP API Endpoints: [\[GET\] /v1/acl/role/:id](/api-docs/acl/roles#read-a-role), [\[GET\] /v1/acl/role/name/:name](/api-docs/acl/roles#read-a-role-by-name)

 The `acl role read` command reads and displays a roles details.

--- a/website/content/commands/acl/role/update.mdx
+++ b/website/content/commands/acl/role/update.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Role Update'

 Command: `consul acl role update`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/role/:id](https://www.consul.io/api-docs/acl/roles#update-a-role)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/role/:id](/api-docs/acl/roles#update-a-role)

 The `acl role update` command is used to update a role. The default operations is to merge the
 current role with those values provided to the command invocation. Therefore to
--- a/website/content/commands/acl/set-agent-token.mdx
+++ b/website/content/commands/acl/set-agent-token.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Set Agent Token'

 Command: `consul acl set-agent-token`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/token/:type](https://www.consul.io/api-docs/agent#update-acl-tokens)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/token/:type](/api-docs/agent#update-acl-tokens)

 This command updates the ACL tokens currently in use by the agent. It can be used to introduce
 ACL tokens to the agent for the first time, or to update tokens that were initially loaded from
--- a/website/content/commands/acl/token/clone.mdx
+++ b/website/content/commands/acl/token/clone.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Token Clone'

 Command: `consul acl token clone`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/token/:AccessorID/clone](https://www.consul.io/api-docs/acl/tokens#clone-a-token)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/token/:AccessorID/clone](/api-docs/acl/tokens#clone-a-token)

 The `acl token clone` command clones an existing token.

--- a/website/content/commands/acl/token/create.mdx
+++ b/website/content/commands/acl/token/create.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Token Create'

 Command: `consul acl token create`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/token](https://www.consul.io/api-docs/acl/tokens#create-a-token)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/token](/api-docs/acl/tokens#create-a-token)

 This command creates new tokens. When creating a new token, policies may be linked using
 either the `-policy-id` or the `-policy-name` options. When specifying policies by IDs you
--- a/website/content/commands/acl/token/delete.mdx
+++ b/website/content/commands/acl/token/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Token Delete'

 Command: `consul acl token delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/token/:AccessorID](https://www.consul.io/api-docs/acl/tokens#delete-a-token)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/acl/token/:AccessorID](/api-docs/acl/tokens#delete-a-token)

 The `acl token delete` command deletes a token.

--- a/website/content/commands/acl/token/list.mdx
+++ b/website/content/commands/acl/token/list.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Token List'

 Command: `consul acl token list`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/tokens](https://www.consul.io/api-docs/acl/tokens#list-tokens)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/tokens](/api-docs/acl/tokens#list-tokens)

 The `acl token list` command lists all tokens. By default it will not show metadata.

--- a/website/content/commands/acl/token/read.mdx
+++ b/website/content/commands/acl/token/read.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Token Read'

 Command: `consul acl token read`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/token/:AccessorID](https://www.consul.io/api-docs/acl/tokens#read-a-token)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/token/:AccessorID](/api-docs/acl/tokens#read-a-token)

 The `acl token read` command reads and displays a token details.

--- a/website/content/commands/acl/token/update.mdx
+++ b/website/content/commands/acl/token/update.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: ACL Token Update'

 Command: `consul acl token update`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/token/:AccessorID](https://www.consul.io/api-docs/acl/tokens#update-a-token)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/acl/token/:AccessorID](/api-docs/acl/tokens#update-a-token)

 The `acl token update` command will update a token. Some parts of the token like whether the
 token is local to the datacenter cannot be changed.
--- a/website/content/commands/acl/translate-rules.mdx
+++ b/website/content/commands/acl/translate-rules.mdx
@ -10,7 +10,7 @@ It will be removed in a future major release when support for the legacy ACL sys

 Command: `consul acl translate-rules`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/rules/translate/:accessor_id](https://www.consul.io/api-docs/acl#translate-a-legacy-token-s-rules)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/acl/rules/translate/:accessor_id](/api-docs/acl#translate-a-legacy-token-s-rules)

 This command translates the legacy ACL rule syntax into the new syntax.

--- a/website/content/commands/catalog/datacenters.mdx
+++ b/website/content/commands/catalog/datacenters.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Catalog List Datacenters'

 Command: `consul catalog datacenters`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/catalog/datacenters](https://www.consul.io/api-docs/catalog#list-datacenters)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/catalog/datacenters](/api-docs/catalog#list-datacenters)

 The `catalog datacenters` command prints all known datacenters.

--- a/website/content/commands/catalog/nodes.mdx
+++ b/website/content/commands/catalog/nodes.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Catalog List Nodes'

 Command: `consul catalog nodes`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/catalog/nodes](https://www.consul.io/api-docs/catalog#list-nodes)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/catalog/nodes](/api-docs/catalog#list-nodes)

 The `catalog nodes` command prints all known nodes and metadata about them.
 It can also query for nodes that match a particular metadata or provide a
--- a/website/content/commands/catalog/services.mdx
+++ b/website/content/commands/catalog/services.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Catalog List Services'

 Command: `consul catalog services`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/catalog/services](https://www.consul.io/api-docs/catalog#list-services)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/catalog/services](/api-docs/catalog#list-services)

 The `catalog services` command prints all known services. It can also query
 for services that match particular metadata or list the services that a
--- a/website/content/commands/config/delete.mdx
+++ b/website/content/commands/config/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Config Delete'

 Command: `consul config delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/config/:kind/:name](https://www.consul.io/api-docs/config#delete-configuration)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/config/:kind/:name](/api-docs/config#delete-configuration)

 The `config delete` command deletes the configuration entry specified by the
 kind and name. See the [configuration entries docs](/docs/agent/config-entries)
--- a/website/content/commands/config/list.mdx
+++ b/website/content/commands/config/list.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Config List'

 Command: `consul config list`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/config/:kind](https://www.consul.io/api-docs/config#list-configurations)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/config/:kind](/api-docs/config#list-configurations)

 The `config list` command lists all given config entries of the given kind.
 See the [configuration entries docs](/docs/agent/config-entries) for more
--- a/website/content/commands/config/read.mdx
+++ b/website/content/commands/config/read.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Config Read'

 Command: `consul config read`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/config/:kind/:name](https://www.consul.io/api-docs/config#get-configuration)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/config/:kind/:name](/api-docs/config#get-configuration)

 The `config read` command reads the config entry specified by the given
 kind and name and outputs its JSON representation. See the
--- a/website/content/commands/config/write.mdx
+++ b/website/content/commands/config/write.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Config Write'

 Command: `consul config write`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/config](https://www.consul.io/api-docs/config#apply-configuration)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/config](/api-docs/config#apply-configuration)

 The `config write` command creates or updates a centralized config entry.
 See the [configuration entries docs](/docs/agent/config-entries) for more
--- a/website/content/commands/connect/ca.mdx
+++ b/website/content/commands/connect/ca.mdx
@ -52,7 +52,7 @@ are not supported from commands, but may be from the corresponding HTTP endpoint

 Usage: `consul connect ca get-config [options]`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/ca/configuration](https://www.consul.io/api-docs/connect/ca#get-ca-configuration)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/ca/configuration](/api-docs/connect/ca#get-ca-configuration)

 #### API Options

@ -87,7 +87,7 @@ are not supported from commands, but may be from the corresponding HTTP endpoint

 Usage: `consul connect ca set-config [options]`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/connect/ca/configuration](https://www.consul.io/api-docs/connect/ca#update-ca-configuration)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/connect/ca/configuration](/api-docs/connect/ca#update-ca-configuration)

 #### API Options

--- a/website/content/commands/event.mdx
+++ b/website/content/commands/event.mdx
@ -13,7 +13,7 @@ description: >-

 Command: `consul event`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/event/fire/:name](https://www.consul.io/api-docs/event#fire-event)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/event/fire/:name](/api-docs/event#fire-event)

 The `event` command provides a mechanism to fire a custom user event to an
 entire datacenter. These events are opaque to Consul, but they can be used
--- a/website/content/commands/exec.mdx
+++ b/website/content/commands/exec.mdx
@ -40,7 +40,7 @@ execute this command.
 | `key:write`     | `"_rexec"` prefix |
 | `event:write`   | `"_rexec"` prefix |

-In addition to the above, the policy associated with the [agent token](https://www.consul.io/docs/security/acl/acl-system#acl-agent-token) should have `write` on `"_rexec"` key prefix. This is for the agents to read the `exec` command and write its output back to the KV store.
+In addition to the above, the policy associated with the [agent token](/docs/security/acl/acl-system#acl-agent-token) should have `write` on `"_rexec"` key prefix. This is for the agents to read the `exec` command and write its output back to the KV store.

 ## Usage

--- a/website/content/commands/force-leave.mdx
+++ b/website/content/commands/force-leave.mdx
@ -11,7 +11,7 @@ description: >-

 Command: `consul force-leave`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/force-leave/:node](https://www.consul.io/api-docs/agent#force-leave-and-shutdown)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/force-leave/:node](/api-docs/agent#force-leave-and-shutdown)

 The `force-leave` command forces a member of a Consul cluster to enter the
 "left" state. The purpose of this method is to force-remove a node that has failed or
--- a/website/content/commands/intention/check.mdx
+++ b/website/content/commands/intention/check.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Intention Check'

 Command: `consul intention check`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/intentions/check](https://www.consul.io/api-docs/connect/intentions#check-intention-result)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/intentions/check](/api-docs/connect/intentions#check-intention-result)

 The `intention check` command checks whether a connection attempt between
 two services would be authorized given the current set of intentions and
--- a/website/content/commands/intention/create.mdx
+++ b/website/content/commands/intention/create.mdx
@ -13,7 +13,7 @@ entry for the destination.

 Command: `consul intention create`

-Corresponding HTTP API Endpoint: [\[POST\] /v1/connect/intentions](https://www.consul.io/api-docs/connect/intentions#create-intention-with-id)
+Corresponding HTTP API Endpoint: [\[POST\] /v1/connect/intentions](/api-docs/connect/intentions#create-intention-with-id)

 The `intention create` command creates or updates an L4 intention.

--- a/website/content/commands/intention/delete.mdx
+++ b/website/content/commands/intention/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Intention Delete'

 Command: `consul intention delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/connect/intentions/exact](https://www.consul.io/api-docs/connect/intentions#delete-intention-by-name)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/connect/intentions/exact](/api-docs/connect/intentions#delete-intention-by-name)

 The `intention delete` command deletes a matching intention.

--- a/website/content/commands/intention/get.mdx
+++ b/website/content/commands/intention/get.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Intention Get'

 Command: `consul intention get`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/intentions/exact](https://www.consul.io/api-docs/connect/intentions##read-specific-intention-by-name)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/intentions/exact](/api-docs/connect/intentions##read-specific-intention-by-name)

 The `intention get` command shows a single intention.

--- a/website/content/commands/intention/list.mdx
+++ b/website/content/commands/intention/list.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Intention List'

 Command: `consul intention list`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/intentions](https://www.consul.io/api-docs/connect/intentions#list-intentions)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/intentions](/api-docs/connect/intentions#list-intentions)

 The `intention list` command shows all intentions including ID and precedence.

--- a/website/content/commands/intention/match.mdx
+++ b/website/content/commands/intention/match.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Intention Match'

 Command: `consul intention match`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/intentions/match](https://www.consul.io/api-docs/connect/intentions#list-matching-intentions)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/connect/intentions/match](/api-docs/connect/intentions#list-matching-intentions)

 The `intention match` command shows the list of intentions that match
 a given source or destination. The list of intentions is listed in evaluation
--- a/website/content/commands/join.mdx
+++ b/website/content/commands/join.mdx
@ -12,7 +12,7 @@ description: >-

 Command: `consul join`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/join/:address](https://www.consul.io/api-docs/agent#join-agent)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/join/:address](/api-docs/agent#join-agent)

 The `join` command tells a Consul agent to join an existing cluster.
 A new Consul agent may join any node in the existing cluster. After joining
--- a/website/content/commands/keyring.mdx
+++ b/website/content/commands/keyring.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Keyring'

 Command: `consul keyring`

-Corresponding HTTP API Endpoints: [\[VARIES\] /v1/operator/keyring](https://www.consul.io/api-docs/operator/keyring)
+Corresponding HTTP API Endpoints: [\[VARIES\] /v1/operator/keyring](/api-docs/operator/keyring)

 The `keyring` command is used to examine and modify the encryption keys used in
 Consul's [Gossip Pools](/docs/internals/gossip). It is capable of
--- a/website/content/commands/kv/delete.mdx
+++ b/website/content/commands/kv/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: KV Delete'

 Command: `consul kv delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/kv/:key](https://www.consul.io/api-docs/kv#delete-key)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/kv/:key](/api-docs/kv#delete-key)

 The `kv delete` command removes the value from Consul's KV store at the
 given path. If no key exists at the path, no action is taken.
--- a/website/content/commands/kv/get.mdx
+++ b/website/content/commands/kv/get.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: KV Get'

 Command: `consul kv get`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/kv/:key](https://www.consul.io/api-docs/kv#read-key)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/kv/:key](/api-docs/kv#read-key)

 The `kv get` command is used to retrieve the value from Consul's KV
 store at the given key name. If no key exists with that name, an error is
--- a/website/content/commands/kv/put.mdx
+++ b/website/content/commands/kv/put.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: KV Put'

 Command: `consul kv put`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/kv/:key](https://www.consul.io/api-docs/kv#create-update-key)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/kv/:key](/api-docs/kv#create-update-key)

 The `kv put` command writes the data to the given path in the KV store.

--- a/website/content/commands/leave.mdx
+++ b/website/content/commands/leave.mdx
@ -11,7 +11,7 @@ description: >-

 Command: `consul leave`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/leave](https://www.consul.io/api-docs/agent#graceful-leave-and-shutdown)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/leave](/api-docs/agent#graceful-leave-and-shutdown)

 The `leave` command triggers a graceful leave and shutdown of the agent.
 It is used to ensure other nodes see the agent as "left" instead of
--- a/website/content/commands/license.mdx
+++ b/website/content/commands/license.mdx
@ -124,7 +124,7 @@ License is valid
 was removed in Consul 1.10. While the CLI command still exists it will
 always return an error. This command will be fully removed in a future release.

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/operator/license](https://www.consul.io/api-docs/operator/license#updating-the-consul-license)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/operator/license](/api-docs/operator/license#updating-the-consul-license)

 This command sets the Consul Enterprise license.

@ -164,7 +164,7 @@ Licensed Features:

 ## get

-Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/license](https://www.consul.io/api-docs/operator/license#getting-the-consul-license)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/license](/api-docs/operator/license#getting-the-consul-license)

 This command gets the Consul Enterprise license.

@ -208,7 +208,7 @@ Licensed Features:
 was removed in Consul 1.10. While the CLI command still exists it will
 always return an error. This command will be fully removed in a future release.

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/operator/license](https://www.consul.io/api-docs/operator/license#resetting-the-consul-license)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/operator/license](/api-docs/operator/license#resetting-the-consul-license)

 Resets license for the datacenter to the one builtin in Consul binary, if it is still valid.
 If the builtin license is invalid, the current one stays active.
--- a/website/content/commands/login.mdx
+++ b/website/content/commands/login.mdx
@ -10,7 +10,7 @@ description: >

 Command: `consul login`

-Corresponding HTTP API Endpoint: [\[POST\] /v1/acl/login](https://www.consul.io/api-docs/acl#login-to-auth-method)
+Corresponding HTTP API Endpoint: [\[POST\] /v1/acl/login](/api-docs/acl#login-to-auth-method)

 The `login` command will exchange the provided third party credentials with the
 requested auth method for a newly minted Consul ACL token. The companion
--- a/website/content/commands/logout.mdx
+++ b/website/content/commands/logout.mdx
@ -10,7 +10,7 @@ description: >

 Command: `consul logout`

-Corresponding HTTP API Endpoint: [\[POST\] /v1/acl/logout](https://www.consul.io/api-docs/acl#logout-from-auth-method)
+Corresponding HTTP API Endpoint: [\[POST\] /v1/acl/logout](/api-docs/acl#logout-from-auth-method)

 The `logout` command will destroy the provided token if it was created from
 `consul login`.
--- a/website/content/commands/maint.mdx
+++ b/website/content/commands/maint.mdx
@ -9,7 +9,7 @@ description: |

 Command: `consul maint`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/maintenance](https://www.consul.io/api-docs/agent#enable-maintenance-mode)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/maintenance](/api-docs/agent#enable-maintenance-mode)

 The `maint` command provides control of service maintenance mode.
 Using the command, it is possible to mark a service provided by a node or all the services on the
--- a/website/content/commands/members.mdx
+++ b/website/content/commands/members.mdx
@ -11,7 +11,7 @@ description: >-

 Command: `consul members`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/agent/members](https://www.consul.io/api-docs/agent#list-members)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/agent/members](/api-docs/agent#list-members)

 The `members` command outputs the current list of members that a Consul
 agent knows about, along with their state. The state of a node can only
--- a/website/content/commands/namespace/create.mdx
+++ b/website/content/commands/namespace/create.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Namespace Create'

 Command: `consul namespace create`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/namespace](https://www.consul.io/api-docs/namespaces#create-a-namespace)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/namespace](/api-docs/namespaces#create-a-namespace)

 <EnterpriseAlert />

--- a/website/content/commands/namespace/delete.mdx
+++ b/website/content/commands/namespace/delete.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Namespace Delete'

 Command: `consul namespace delete`

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/namespace/:name](https://www.consul.io/api-docs/namespaces#delete-a-namespace)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/namespace/:name](/api-docs/namespaces#delete-a-namespace)

 <EnterpriseAlert />

--- a/website/content/commands/namespace/list.mdx
+++ b/website/content/commands/namespace/list.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Namespace List'

 Command: `consul namespace list`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/namespaces](https://www.consul.io/api-docs/namespaces#list-all-namespaces)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/namespaces](/api-docs/namespaces#list-all-namespaces)

 <EnterpriseAlert />

--- a/website/content/commands/namespace/read.mdx
+++ b/website/content/commands/namespace/read.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Namespace Read'

 Command: `consul namespace read`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/namespace/:name](https://www.consul.io/api-docs/namespaces#read-a-namespace)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/namespace/:name](/api-docs/namespaces#read-a-namespace)

 <EnterpriseAlert />

--- a/website/content/commands/namespace/update.mdx
+++ b/website/content/commands/namespace/update.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Namespace Update'

 Command: `consul namespace update`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/namespace/:name](https://www.consul.io/api-docs/namespaces#update-a-namespace)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/namespace/:name](/api-docs/namespaces#update-a-namespace)

 <EnterpriseAlert />

--- a/website/content/commands/namespace/write.mdx
+++ b/website/content/commands/namespace/write.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Namespace Write'

 Command: `consul namespace write`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/namespace/:name](https://www.consul.io/api-docs/namespaces#update-a-namespace)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/namespace/:name](/api-docs/namespaces#update-a-namespace)

 <EnterpriseAlert />

--- a/website/content/commands/operator/area.mdx
+++ b/website/content/commands/operator/area.mdx
@ -47,7 +47,7 @@ read or write privileges to use these commands.

 ## create

-Corresponding HTTP API Endpoint: [\[POST\] /v1/operator/area](https://www.consul.io/api-docs/operator/area#create-network-area)
+Corresponding HTTP API Endpoint: [\[POST\] /v1/operator/area](/api-docs/operator/area#create-network-area)

 This command creates a new network area.

@ -89,7 +89,7 @@ The return code will indicate success or failure.

 ## delete

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/operator/area/:uuid](https://www.consul.io/api-docs/operator/area#delete-network-area)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/operator/area/:uuid](/api-docs/operator/area#delete-network-area)

 This command deletes an existing network area.

@ -127,7 +127,7 @@ The return code will indicate success or failure.

 ## join

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/operator/area/:uuid/join](https://www.consul.io/api-docs/operator/area#join-network-area)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/operator/area/:uuid/join](/api-docs/operator/area#join-network-area)

 This command joins Consul servers into an existing network area by address, such as
 an IP or hostname with an optional port. Multiple addresses may be given.
@ -172,7 +172,7 @@ The return code will indicate success or failure.

 ## list

-Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/area](https://www.consul.io/api-docs/operator/area#list-network-areas)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/area](/api-docs/operator/area#list-network-areas)

 This command lists all network areas.

@ -210,7 +210,7 @@ The return code will indicate success or failure.

 ## members

-Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/area/:uuid/members](https://www.consul.io/api-docs/operator/area#list-network-area-members)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/area/:uuid/members](/api-docs/operator/area#list-network-area-members)

 This command displays Consul server nodes present in a network area, or all
 areas if no area is specified.
@ -275,7 +275,7 @@ The return code will indicate success or failure.

 ## update

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/operator/area/:uuid](https://www.consul.io/api-docs/operator/area#update-network-area)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/operator/area/:uuid](/api-docs/operator/area#update-network-area)

 This command updates the configuration of network area.

--- a/website/content/commands/operator/autopilot.mdx
+++ b/website/content/commands/operator/autopilot.mdx
@ -28,7 +28,7 @@ Subcommands:

 ## get-config

-Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/autopilot/configuration](https://www.consul.io/api-docs/operator/autopilot#read-configuration)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/autopilot/configuration](/api-docs/operator/autopilot#read-configuration)

 This command displays the current autopilot configuration.

@ -63,7 +63,7 @@ UpgradeMigrationTag = ""

 ## set-config

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/operator/autopilot/configuration](https://www.consul.io/api-docs/operator/autopilot#update-configuration)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/operator/autopilot/configuration](/api-docs/operator/autopilot#update-configuration)

 Modifies the current Autopilot configuration.

@ -121,7 +121,7 @@ The return code will indicate success or failure.

 ## state

-Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/autopilot/state](https://www.consul.io/api-docs/operator/autopilot#read-the-autopilot-state)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/operator/autopilot/state](/api-docs/operator/autopilot#read-the-autopilot-state)

 This command displays the current autopilot state.

--- a/website/content/commands/operator/raft.mdx
+++ b/website/content/commands/operator/raft.mdx
@ -29,7 +29,7 @@ Subcommands:

 ## list-peers

-Corresponding HTTP API Endpoint: [\[GET\] /v1/status/peers](https://www.consul.io/api-docs/status#list-raft-peers)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/status/peers](/api-docs/status#list-raft-peers)

 This command displays the current Raft peer configuration.

@ -72,7 +72,7 @@ configuration.

 ## remove-peer

-Corresponding HTTP API Endpoint: [\[DELETE\] /v1/operator/raft/peer](https://www.consul.io/api-docs/operator/raft#delete-raft-peer)
+Corresponding HTTP API Endpoint: [\[DELETE\] /v1/operator/raft/peer](/api-docs/operator/raft#delete-raft-peer)

 This command removes the Consul server with given address from the Raft configuration.

--- a/website/content/commands/reload.mdx
+++ b/website/content/commands/reload.mdx
@ -8,7 +8,7 @@ description: The `reload` command triggers a reload of configuration files for t

 Command: `consul reload`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/reload](https://www.consul.io/api-docs/agent#reload-agent)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/reload](/api-docs/agent#reload-agent)

 The `reload` command triggers a reload of configuration files for the agent.

--- a/website/content/commands/rtt.mdx
+++ b/website/content/commands/rtt.mdx
@ -9,7 +9,7 @@ description: |

 Command: `consul rtt`

-Corresponding HTTP API Endpoints: [\[GET\] /v1/coordinate/datacenters](https://www.consul.io/api-docs/coordinate#read-wan-coordinates), [\[GET\] /v1/coordinate/nodes](https://www.consul.io/api-docs/coordinate#read-lan-coordinates-for-all-nodes)
+Corresponding HTTP API Endpoints: [\[GET\] /v1/coordinate/datacenters](/api-docs/coordinate#read-wan-coordinates), [\[GET\] /v1/coordinate/nodes](/api-docs/coordinate#read-lan-coordinates-for-all-nodes)

 The `rtt` command estimates the network round trip time between two nodes using
 Consul's network coordinate model of the cluster.
--- a/website/content/commands/services/deregister.mdx
+++ b/website/content/commands/services/deregister.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Services Deregister'

 Command: `consul services deregister`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/service/deregister/:service_id](https://www.consul.io/api-docs/agent/service#deregister-service)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/service/deregister/:service_id](/api-docs/agent/service#deregister-service)

 The `services deregister` command deregisters a service with the local agent.
 Note that this command can only deregister services that were registered
--- a/website/content/commands/services/register.mdx
+++ b/website/content/commands/services/register.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Services Register'

 Command: `consul services register`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/service/register](https://www.consul.io/api-docs/agent/service#register-service)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/service/register](/api-docs/agent/service#register-service)

 The `services register` command registers a service with the local agent.
 This command returns after registration and must be paired with explicit
--- a/website/content/commands/snapshot/restore.mdx
+++ b/website/content/commands/snapshot/restore.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Snapshot Restore'

 Command: `consul snapshot restore`

-Corresponding HTTP API Endpoint: [\[PUT\] /v1/snapshot](https://www.consul.io/api-docs/snapshot#restore-snapshot)
+Corresponding HTTP API Endpoint: [\[PUT\] /v1/snapshot](/api-docs/snapshot#restore-snapshot)

 The `snapshot restore` command is used to restore an atomic, point-in-time
 snapshot of the state of the Consul servers which includes key/value entries,
--- a/website/content/commands/snapshot/save.mdx
+++ b/website/content/commands/snapshot/save.mdx
@ -7,7 +7,7 @@ page_title: 'Commands: Snapshot Save'

 Command: `consul snapshot save`

-Corresponding HTTP API Endpoint: [\[GET\] /v1/snapshot](https://www.consul.io/api-docs/snapshot#generate-snapshot)
+Corresponding HTTP API Endpoint: [\[GET\] /v1/snapshot](/api-docs/snapshot#generate-snapshot)

 The `snapshot save` command is used to retrieve an atomic, point-in-time snapshot
 of the state of the Consul servers which includes key/value entries,