Consul: Manually migrate missing docs (#1474)

### Description

After noticing that some changes merged into the Consul docs before the
migration to UDR were missing, I went back and did a manual account of
the histories for both the `main` and `release/v1.22.x` branches of the
`hashicorp/consul` repo. As far as I can tell, changes merged into the
repo in October were not migrated.

This PR merges most of those missing changes. Redirect related fixes are
being included in a dedicated redirect PR.

Author: boruszak

content/consul/v1.22.x/content/api-docs/agent/index.mdx

@@ -660,7 +660,7 @@ The corresponding CLI command is [`consul join`](/consul/commands/join).
 
 ### Path Parameters
 
-- `address` `(string: <required>)` - Specifies the address of the other agent to join.
+- `address` `(string: <required>)` - Specifies the address of the other agent to join. You can specifiy either an IPv4 or an IPv6 address.
 
 ### Query Parameters
 

content/consul/v1.22.x/content/api-docs/agent/service.mdx

@@ -628,7 +628,12 @@ The `/agent/service/register` endpoint supports camel case and _snake case_ for
   This field takes precedence over the `ns` query parameter,
   one of several [other methods to specify the namespace](#methods-to-specify-namespace).
 
-- `Port` `(int: 0)` - Specifies the port of the service.
+- `Port` `(int: 0)` - Specifies the port of the service. This field is mutually exclusive with the `Ports` field. You can use this field in both service discovery and service mesh use cases.
+
+- `Ports` `(array<Port>: nil)` - Specifies multiple ports for a service. This field is mutually exclusive with the `Port` field. Consul supports multi-port services for service discovery use cases only. For an example service definition, refer to [Multi-port service definition](#multi-port-service-definition). You can specify the following values:
+  - `name` `(string: "")` - Specifies a name for the port. This value is addressable with Consul DNS.
+  - `port` `(int: 0)` - Specifies a numeric port where the service is available. 
+  - `default` `(bool: false)` - Sets a port as the default service when a port is not included. 
 
 - `Kind` `(string: "")` - The kind of service. Defaults to `""`, which is a
   typical Consul service. You can specify the following values: 

content/consul/v1.22.x/content/api-docs/operator/audit.mdx

@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: Audit - Operator - HTTP API
+description: |-
+  The /operator/audit endpoints expose audit log information via Consul's HTTP API.
+---
+
+# Audit logs - Operator HTTP API
+
+<EnterpriseAlert />
+
+The `/operator/audit` endpoints provide tools to interact with Consul's audit 
+logging subsystem through Consul's HTTP API.
+
+The audit logging functionality described here is available only in
+[Consul Enterprise](https://www.hashicorp.com/products/consul/) version 1.8.0 and
+later. 
+
+Refer to the [audit logging documentation](/consul/docs/monitor/log/audit) for workflow guidance and additional information.
+
+## Calculate data hash
+
+This endpoint calculates the hash of the data used by the audit log hash function and salt.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `POST` | `/operator/audit-hash`         | `application/json` |
+
+The following table shows this endpoint's support for
+[blocking queries](/consul/api-docs/features/blocking),
+[consistency modes](/consul/api-docs/features/consistency),
+[agent caching](/consul/api-docs/features/caching), and
+[required ACLs](/consul/api-docs/api-structure#authentication).
+
+| Blocking Queries | Consistency Modes | Agent Caching | ACL Required    |
+| ---------------- | ----------------- | ------------- | --------------- |
+| `NO`             | `none`            | `none`        | `operator:read` |
+
+The corresponding CLI command is [`consul operator audit hash`](/consul/commands/operator/audit#hash).
+
+### JSON request body schema
+
+- `Input` `(string: <required>)` - Specifies the input string to hash.
+
+### Sample payload
+
+```json
+{
+  "Input": "test"
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    http://127.0.0.1:8500/v1/operator/audit-hash
+```
+
+### Sample response
+
+```json
+{
+  "Hash": "hmac_sha256:794c39dbc00d4714740199fe79982d02bbc5d303ab73149dfabc1244e3df3d4c"
+}
+```

content/consul/v1.22.x/content/api-docs/operator/utilization.mdx

@@ -0,0 +1,92 @@
+---
+layout: api
+page_title: Utilization - Operator - HTTP API
+description: |-
+  The /operator/utilization endpoints generate a Consul utilization bundle for license reporting.
+---
+
+# Utilization - Operator HTTP API
+
+<EnterpriseAlert />
+
+The `/operator/utilization` endpoints provide tools to generate a Consul utilization bundle for license reporting.
+
+Refer to the [Manual license utilization reporting documentation](/consul/docs/enterprise/license/reporting#manual-license-utilization-reporting) for more information.
+
+## Generate utilization bundle
+
+This endpoint generates a Consul utilization bundle for license reporting.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET` | `/operator/utilization`         | `application/json` |
+
+The following table shows this endpoint's support for
+[blocking queries](/consul/api-docs/features/blocking),
+[consistency modes](/consul/api-docs/features/consistency),
+[agent caching](/consul/api-docs/features/caching), and
+[required ACLs](/consul/api-docs/api-structure#authentication).
+
+| Blocking Queries | Consistency Modes | Agent Caching | ACL Required    |
+| ---------------- | ----------------- | ------------- | --------------- |
+| `NO`             | `none`            | `none`        | `operator:read` |
+
+The corresponding CLI command is [`consul operator utilization`](/consul/commands/operator/utilization).
+
+
+### Query parameters
+
+- `message`  `(string: "")` - Optional context that is logged with the utilization export.
+
+- `today_only` `(bool: false)` - Include only the most recent utilization snapshot.
+
+- `send_report` `(bool: false)` - Automatically send the utilization report to HashiCorp.
+
+### Sample request
+
+```shell-session
+$ curl \
+    http://127.0.0.1:8500/v1/operator/utilization
+```
+
+### Sample response
+
+```json
+{
+  "version": "2",
+  "mode": "manual",
+  "timestamp": "2025-10-09T15:23:48.354524388Z",
+  "signature": "9ea44420679b3776d1636acbe9ec1f636a58bd4a5b7f2b215cc2958084ded505",
+  "checksum": 17512992959032736032,
+  "snapshots": [
+    {
+      "snapshot_version": 2,
+      "id": "0001MEFMW4B0G5JJHKQN4T9RCE",
+      "timestamp": "2025-10-09T15:23:48.348542971Z",
+      "schema_version": "2.0.0",
+      "product": "consul",
+      "process_id": "01K6FXJDTFBQQP5B3RAXRFRB1K",
+      "metrics": {
+        "consul.billable.nodes": {
+          "key": "consul.billable.nodes",
+          "value": 7,
+          "mode": "write"
+        },
+        "consul.billable.service_instances": {
+          "key": "consul.billable.service_instances",
+          "value": 4,
+          "mode": "write"
+        }
+      },
+      "product_version": "1.22.0-rc1+ent",
+      "license_id": "642088be-c801-c34a-bb5c-e70d4feb18fe",
+      "checksum": 18094916709627403007,
+      "metadata": {
+        "billing_start": "2021-09-30T00:00:00Z",
+        "cluster_id": "dc1"
+      }
+    }
+  ]
+}
+```
+

content/consul/v1.22.x/content/commands/agent.mdx

@@ -37,7 +37,7 @@ information.
   a very large output in their checks. In order to completely disable check output
   capture, it is possible to use [`discard_check_output`](/consul/docs/reference/agent/configuration-file/general#discard_check_output).
 
-- `-client` ((#\_client)) - The address to which Consul will bind client
+- `-client` ((#\_client)) - The IPV4 or IPv6 address to which Consul will bind client
   interfaces, including the HTTP and DNS servers. By default, this is "127.0.0.1",
   allowing only loopback connections. In Consul 1.0 and later this can be set to
   a space-separated list of addresses to bind to, or a [go-sockaddr]
@@ -203,11 +203,11 @@ information.
 ## Address Bind Options
 
 - `-bind` ((#\_bind)) - The address that should be bound to for internal
-  cluster communications. This is an IP address that should be reachable by all other
-  nodes in the cluster. By default, this is "0.0.0.0", meaning Consul will bind to
+  cluster communications. This is an IPv4 or IPv6 address that should be reachable by all other
+  nodes in the cluster. By default, this is `0.0.0.0`, meaning Consul will bind to
   all addresses on the local machine and will [advertise](#_advertise)
-  the private IPv4 address to the rest of the cluster. If there are multiple private
-  IPv4 addresses available, Consul will exit with an error at startup. If you specify
+  the private IPv4 or IPv6 address to the rest of the cluster. If there are multiple private
+  IPv4 or IPv6 addresses available, Consul will exit with an error at startup. If you specify
   `"[::]"`, Consul will [advertise](#_advertise) the public
   IPv6 address. If there are multiple public IPv6 addresses available, Consul will
   exit with an error at startup. Consul uses both TCP and UDP and the same port for
@@ -238,14 +238,14 @@ information.
 
   </CodeBlockConfig>
 
-- `-serf-wan-bind` ((#\_serf_wan_bind)) - The address that should be bound
+- `-serf-wan-bind` ((#\_serf_wan_bind)) - The IPv4 or IPv6 address that should be bound
   to for Serf WAN gossip communications. By default, the value follows the same rules
   as [`-bind` command-line flag](#_bind), and if this is not specified, the `-bind`
   option is used. This is available in Consul 0.7.1 and later. In Consul 1.1.0 and later this can be dynamically defined with a [go-sockaddr]
   template that is resolved at runtime.
 
 - `-serf-lan-bind` ((#\_serf_lan_bind)) - The address that should be bound
-  to for Serf LAN gossip communications. This is an IP address that should be reachable
+  to for Serf LAN gossip communications. This is an IPv4 or IPv6 address that should be reachable
   by all other LAN nodes in the cluster. By default, the value follows the same rules
   as [`-bind` command-line flag](#_bind), and if this is not specified, the `-bind`
   option is used. This is available in Consul 0.7.1 and later. In Consul 1.1.0 and later this can be dynamically defined with a [go-sockaddr]
@@ -271,7 +271,7 @@ information.
 ## Configuration File Options
 
 - `-config-file` ((#\_config_file)) - A configuration file to load. For
-  more information on the format of this file, read the [Configuration Files](/consul/docs/reference/agent)
+  more information on the format of this file, read the [Configuration Files](/consul/docs/reference/agent/configuration-file)
   section. This option can be specified multiple times to load multiple configuration
   files. If it is specified multiple times, configuration files loaded later will
   merge with configuration files loaded earlier. During a config merge, single-value
@@ -284,7 +284,7 @@ information.
   the [`config-file`](#_config_file) option above. This option can be specified multiple
   times to load multiple directories. Sub-directories of the config directory are
   not loaded. For more information on the format of the configuration files, refer to
-  the [Configuration Files](/consul/docs/reference/agent) section.
+  the [Configuration Files](/consul/docs/reference/agent/configuration-file) section.
 
 - `-config-format` ((#\_config_format)) - The format of the configuration
   files to load. Normally, Consul detects the format of the config files from the
@@ -295,7 +295,7 @@ information.
 ## DNS and Domain Options
 
 - `-dns-port` ((#\_dns_port)) - the DNS port to listen on. This overrides
-  the default port 8600. This is available in Consul 0.7 and later.
+  the default port `8600`. This is available in Consul 0.7 and later.
 
 - `-domain` ((#\_domain)) - By default, Consul responds to DNS queries in
   the "consul." domain. This flag can be used to change that domain. All queries

content/consul/v1.22.x/content/commands/force-leave.mdx

@@ -57,7 +57,7 @@ consul force-leave ec2-001-staging
 ```
 
 When run on a server that is part of a
-[WAN gossip pool](/consul/tutorials/networking/federation-gossip-wan),
+[WAN gossip pool](/consul/docs/east-west/wan-federation/vms),
 `force-leave` can remove failed servers in other datacenters from the WAN pool.
 
 The identifying node-name in a WAN pool is `[node-name].[datacenter]`.

content/consul/v1.22.x/content/commands/index.mdx

@@ -138,19 +138,35 @@ These environment variables and their purpose are described below:
 
 ### `CONSUL_HTTP_ADDR`
 
-This is the HTTP API address to the _local_ Consul agent
-(not the remote server) specified as a URI with optional scheme:
+This variable specifies the IPv4 or IPv 6 address of the Consul agent you want to interact with locally, specified as a URI with optional scheme.
+
+<Tabs>
+
+<Tab heading="IPv4">
 
 ```
 CONSUL_HTTP_ADDR=127.0.0.1:8500
 ```
 
-or as a Unix socket path:
+</Tab>
+
+<Tab heading="IPv6">
+
+```
+CONSUL_HTTP_ADDR=2001:db8:3333:4444:5555:6666:7777:8888
+```
+
+</Tab>
+
+<Tab heading="Unix socket path">
 
 ```
 CONSUL_HTTP_ADDR=unix:///var/run/consul_http.sock
 ```
 
+</Tab>
+</Tabs>
+
 If the `https://` scheme is used, `CONSUL_HTTP_SSL` is implied to be true.
 
 ### `CONSUL_HTTP_TOKEN`
@@ -240,7 +256,7 @@ CONSUL_TLS_SERVER_NAME=consulserver.domain
 
 ### `CONSUL_GRPC_ADDR`
 
-Like [`CONSUL_HTTP_ADDR`](#consul_http_addr) but configures the address the
+Like [`CONSUL_HTTP_ADDR`](#consul_http_addr) but configures the IPv4 or IPv6 address the
 local agent is listening for gRPC requests. Currently gRPC is only used for
 integrating [Envoy proxy](/consul/docs/reference/proxy/envoy) and must be [enabled
 explicitly](/consul/docs/reference/agent/configuration-file/general#grpc_port) in agent configuration.

content/consul/v1.22.x/content/commands/join.mdx

@@ -14,7 +14,7 @@ Command: `consul join`
 
 Corresponding HTTP API Endpoint: [\[PUT\] /v1/agent/join/:address](/consul/api-docs/agent#join-agent)
 
-The `join` command tells a Consul agent to join an existing cluster.
+The `join` command tells a Consul agent to join an existing cluster at the indicated IPv4 or IPv6 address.
 A new Consul agent may join any node in the existing cluster. After joining
 with one member, the gossip communication will propagate the updated membership
 state across the cluster.

content/consul/v1.22.x/content/commands/operator/audit.mdx

@@ -0,0 +1,72 @@
+---
+layout: commands
+page_title: 'Commands: Operator Audit'
+description: >
+  Use the operator audit command to interact with Consul's audit logging subsystem.
+---
+
+# Consul Operator Audit
+
+Command: `consul operator audit`
+
+<EnterpriseAlert />
+
+Consul Enterprise audit logging captures a list of authenticated events that 
+Consul processes through its HTTP API. Use the `operator audit` command to 
+interact with Consul's audit logging subsystem.
+
+Fore information and workflow guidance, refer to the [audit logging documentation](/consul/docs/monitor/log/audit).
+
+```text
+Usage: consul operator audit <subcommand> [options]
+  The Audit operator command is used to interact with Consul's Audit logging subsystem. The
+  command can be used to calculate the audit log hash of a given string.
+
+Subcommands:
+    hash    Computes the audit hash of a string
+```
+
+If ACLs are enabled, the client must supply an ACL Token with `operator`
+read or write privileges to use these commands.
+
+## hash
+
+Corresponding HTTP API Endpoint: [\[POST\] /v1/operator/audit-hash](/consul/api-docs/operator/audit)
+
+Computes the audit hash of a string. Optionally compare the computed hash to a specified hash.
+
+The following table shows this command's [required ACLs](/consul/api-docs/api-structure#authentication). Commands do not support configuration of
+[blocking queries](/consul/api-docs/features/blocking) or [agent caching](/consul/api-docs/features/caching), but the corresponding HTTP endpoint may support that configuration.
+
+| ACL Required     |
+| ---------------- |
+| `operator:read`  |
+
+Usage: `consul operator audit hash -input INPUT [options]`
+
+#### API options
+
+@include 'legacy/http_api_options_client.mdx'
+
+@include 'legacy/http_api_options_server.mdx'
+
+#### Command options
+
+- `-hash-to-match=<string>` - Optional. If specified, the command outputs whether this value matches the computed hash of the 'input' value. Should be in the format: `hmac_sha256:xxxx`
+
+- `-input=<string>` - Specifies the input string to hash. This flag is required.
+
+### Examples
+
+This example displays the audit hash of the provided value.
+
+```shell-session
+$ consul operator audit hash -input="my-value"
+```
+
+This example compares the audit hash of a provided value.
+
+```
+$ consul operator audit hash -input="my-value" -hash-to-match="hmac_sha256:37ed9ed..."
+```
+