Merge pull request hashicorp#12024 from hashicorp/docs/update-links-t…

…o-avoid-redirects

docs: Avoid redirects by pointing links to new URLs

website/components/footer/index.jsx

@@ -8,7 +8,7 @@ export default function Footer({ openConsentManager }) {
           <Link href="/intro">
             <a>Intro</a>
           </Link>
-          <Link href="/guides">
+          <Link href="/docs/guides">
             <a>Guides</a>
           </Link>
           <Link href="/docs">

website/content/api-docs/acl/auth-methods.mdx

@@ -44,7 +44,7 @@ The corresponding CLI command is [`consul acl auth-method create`](/commands/acl
 
 - `Type` `(string: <required>)` - The type of auth method being configured.
   This field is immutable. For allowed values see the [auth method
-  documentation](/docs/acl/auth-methods).
+  documentation](/docs/security/acl/auth-methods).
 
 - `Description` `(string: "")` - Free form human readable description of the
   auth method.
@@ -69,7 +69,7 @@ The corresponding CLI command is [`consul acl auth-method create`](/commands/acl
 - `Config` `(map[string]string: <required>)` - The raw configuration to use for
   the chosen auth method. Contents will vary depending upon the type chosen.
   For more information on configuring specific auth method types, see the [auth
-  method documentation](/docs/acl/auth-methods).
+  method documentation](/docs/security/acl/auth-methods).
 
 - `Namespace` `(string: "")` <EnterpriseAlert inline /> - Specifies the namespace to
   create the auth method within. If not provided in the JSON body, the value of
@@ -252,7 +252,7 @@ The corresponding CLI command is [`consul acl auth-method update`](/commands/acl
 - `Config` `(map[string]string: <required>)` - The raw configuration to use for
   the chosen auth method. Contents will vary depending upon the type chosen.
   For more information on configuring specific auth method types, see the [auth
-  method documentation](/docs/acl/auth-methods).
+  method documentation](/docs/security/acl/auth-methods).
 
 - `Namespace` `(string: "")` <EnterpriseAlert inline /> - Specifies the namespace of
   the auth method to update. If not provided in the JSON body, the value of

website/content/api-docs/acl/index.mdx

@@ -276,7 +276,7 @@ agent_prefix "" {
 ## Login to Auth Method
 
 This endpoint was added in Consul 1.5.0 and is used to exchange an [auth
-method](/docs/acl/auth-methods) bearer token for a newly-created
+method](/docs/security/acl/auth-methods) bearer token for a newly-created
 Consul ACL token.
 
 | Method | Path         | Produces           |
@@ -407,7 +407,7 @@ $ curl \
 </EnterpriseAlert>
 
 This endpoint was added in Consul 1.8.0 and is used to obtain an authorization
-URL from Consul to start an [OIDC login flow](/docs/acl/auth-methods/oidc).
+URL from Consul to start an [OIDC login flow](/docs/security/acl/auth-methods/oidc).
 
 | Method | Path                 | Produces           |
 | ------ | -------------------- | ------------------ |
@@ -433,10 +433,10 @@ replication enabled.
 ### Parameters
 
 - `AuthMethod` `(string: <required>)` - The name of the auth method to use for
-  login. This must be of type [`oidc`](/docs/acl/auth-methods/oidc).
+  login. This must be of type [`oidc`](/docs/security/acl/auth-methods/oidc).
 
 - `RedirectURI` `(string: <required>)` - See [Redirect
-  URIs](/docs/acl/auth-methods/oidc#redirect-uris) for more information.
+  URIs](/docs/security/acl/auth-methods/oidc#redirect-uris) for more information.
 
 - `ClientNonce` `(string: "")` - Optional client-provided nonce that must match
   during callback, if present.
@@ -513,7 +513,7 @@ replication enabled.
 ### Parameters
 
 - `AuthMethod` `(string: <required>)` - The name of the auth method to use for
-  login. This must be of type [`oidc`](/docs/acl/auth-methods/oidc).
+  login. This must be of type [`oidc`](/docs/security/acl/auth-methods/oidc).
 
 - `State` `(string: <required>)` - Opaque state ID that is part of the
   Authorization URL and will be included in the the redirect following

website/content/api-docs/acl/legacy.mdx

@@ -45,7 +45,7 @@ The table below shows this endpoint's support for
   are: `client` and `management`.
 
 - `Rules` `(string: "")` - Specifies rules for this ACL token. The format of the
-  `Rules` property is detailed in the [ACL Rule documentation](/docs/acl/acl-rules).
+  `Rules` property is detailed in the [ACL Rule documentation](/docs/security/acl/acl-rules).
 
 ### Sample Payload
 
@@ -296,4 +296,4 @@ $ curl \
 
 ## Check ACL Replication
 
-The check ACL replication endpoint has not changed between the legacy system and the new system. Review the [latest documentation](/api/acl/acl#check-acl-replication) to learn more about this endpoint.
+The check ACL replication endpoint has not changed between the legacy system and the new system. Review the [latest documentation](/api-docs/acl#check-acl-replication) to learn more about this endpoint.

website/content/api-docs/acl/policies.mdx

@@ -44,7 +44,7 @@ The corresponding CLI command is [`consul acl policy create`](/commands/acl/poli
 - `Description` `(string: "")` - Free form human readable description of the policy.
 
 - `Rules` `(string: "")` - Specifies rules for the ACL policy. The format of the
-  `Rules` property is detailed in the [ACL Rules documentation](/docs/acl/acl-rules).
+  `Rules` property is detailed in the [ACL Rules documentation](/docs/security/acl/acl-rules).
 
 - `Datacenters` `(array<string>)` - Specifies the datacenters the policy is valid within.
   When no datacenters are provided the policy is valid in all datacenters including
@@ -227,7 +227,7 @@ The corresponding CLI command is [`consul acl policy update`](/commands/acl/poli
 - `Description` `(string: "")` - Free form human readable description of this policy.
 
 - `Rules` `(string: "")` - Specifies rules for this ACL policy. The format of the
-  `Rules` property is detailed in the [ACL Rules documentation](/docs/acl/acl-rules).
+  `Rules` property is detailed in the [ACL Rules documentation](/docs/security/acl/acl-rules).
 
 - `Datacenters` `(array<string>)` - Specifies the datacenters this policy is valid within.
   When no datacenters are provided the policy is valid in all datacenters including

website/content/api-docs/acl/roles.mdx

@@ -50,7 +50,7 @@ The corresponding CLI command is [`consul acl role create`](/commands/acl/role/c
   breaking tokens.
 
 - `ServiceIdentities` `(array<ServiceIdentity>)` - The list of [service
-  identities](/docs/acl/acl-system#acl-service-identities) that should be
+  identities](/docs/security/acl/acl-system#acl-service-identities) that should be
   applied to the role. Added in Consul 1.5.0.
 
   - `ServiceName` `(string: <required>)` - The name of the service. The name
@@ -64,7 +64,7 @@ The corresponding CLI command is [`consul acl role create`](/commands/acl/role/c
     but may in the future.
 
 - `NodeIdentities` `(array<NodeIdentity>)` - The list of [node
-  identities](/docs/acl/acl-system#acl-node-identities) that should be
+  identities](/docs/security/acl/acl-system#acl-node-identities) that should be
   applied to the role. Added in Consul 1.8.1.
 
   - `NodeName` `(string: <required>)` - The name of the node. The name
@@ -339,11 +339,11 @@ The corresponding CLI command is [`consul acl role update`](/commands/acl/role/u
   breaking tokens.
 
 - `ServiceIdentities` `(array<ServiceIdentity>)` - The list of [service
-  identities](/docs/acl/acl-system#acl-service-identities) that should be
+  identities](/docs/security/acl/acl-system#acl-service-identities) that should be
   applied to the role. Added in Consul 1.5.0.
 
 - `NodeIdentities` `(array<NodeIdentity>)` - The list of [node
-  identities](/docs/acl/acl-system#acl-node-identities) that should be
+  identities](/docs/security/acl/acl-system#acl-node-identities) that should be
   applied to the role. Added in Consul 1.8.1.
 
 - `Namespace` `(string: "")` <EnterpriseAlert inline /> - Specifies the namespace of

website/content/api-docs/acl/tokens.mdx

@@ -62,7 +62,7 @@ The corresponding CLI command is [`consul acl token create`](/commands/acl/token
   enables role renaming without breaking tokens. Added in Consul 1.5.0.
 
 - `ServiceIdentities` `(array<ServiceIdentity>)` - The list of [service
-  identities](/docs/acl/acl-system#acl-service-identities) that should be
+  identities](/docs/security/acl/acl-system#acl-service-identities) that should be
   applied to the token. Added in Consul 1.5.0.
 
   - `ServiceName` `(string: <required>)` - The name of the service. The name
@@ -76,7 +76,7 @@ The corresponding CLI command is [`consul acl token create`](/commands/acl/token
     but may in the future.
 
 - `NodeIdentities` `(array<NodeIdentity>)` - The list of [node
-  identities](/docs/acl/acl-system#acl-node-identities) that should be
+  identities](/docs/security/acl/acl-system#acl-node-identities) that should be
   applied to the token. Added in Consul 1.8.1.
 
   - `NodeName` `(string: <required>)` - The name of the node. The name
@@ -329,7 +329,7 @@ The corresponding CLI command is [`consul acl token update`](/commands/acl/token
   enables role renaming without breaking tokens.
 
 - `ServiceIdentities` `(array<ServiceIdentity>)` - The list of [service
-  identities](/docs/acl/acl-system#acl-service-identities) that should be
+  identities](/docs/security/acl/acl-system#acl-service-identities) that should be
   applied to the token. Added in Consul 1.5.0.
 
   - `ServiceName` `(string: <required>)` - The name of the service. The name
@@ -343,7 +343,7 @@ The corresponding CLI command is [`consul acl token update`](/commands/acl/token
     but may in the future.
 
 - `NodeIdentities` `(array<NodeIdentity>)` - The list of [node
-  identities](/docs/acl/acl-system#acl-node-identities) that should be
+  identities](/docs/security/acl/acl-system#acl-node-identities) that should be
   applied to the token. Added in Consul 1.8.1.
 
   - `NodeName` `(string: <required>)` - The name of the node. The name

website/content/api-docs/agent/check.mdx

@@ -18,7 +18,7 @@ using the HTTP API.
 It is important to note that the checks known by the agent may be different from
 those reported by the catalog. This is usually due to changes being made while
 there is no leader elected. The agent performs active
-[anti-entropy](/docs/internals/anti-entropy), so in most situations
+[anti-entropy](/docs/architecture/anti-entropy), so in most situations
 everything will be in sync within a few seconds.
 
 | Method | Path            | Produces           |

website/content/api-docs/agent/index.mdx

@@ -12,7 +12,7 @@ The `/agent` endpoints are used to interact with the local Consul agent.
 Usually, services and checks are registered with an agent which then takes on
 the burden of keeping that data synchronized with the cluster. For example, the
 agent registers services and checks with the Catalog and performs
-[anti-entropy](/docs/internals/anti-entropy) to recover from outages.
+[anti-entropy](/docs/architecture/anti-entropy) to recover from outages.
 
 In addition to these endpoints, additional endpoints are grouped in the
 navigation for `Checks` and `Services`.

website/content/api-docs/agent/service.mdx

@@ -20,7 +20,7 @@ or added dynamically using the HTTP API.
 It is important to note that the services known by the agent may be different
 from those reported by the catalog. This is usually due to changes being made
 while there is no leader elected. The agent performs active
-[anti-entropy](/docs/internals/anti-entropy), so in most situations
+[anti-entropy](/docs/architecture/anti-entropy), so in most situations
 everything will be in sync within a few seconds.
 
 | Method | Path              | Produces           |
@@ -137,7 +137,7 @@ configuration that was registered with the instance.
 It is important to note that the services known by the agent may be different
 from those reported by the catalog. This is usually due to changes being made
 while there is no leader elected. The agent performs active
-[anti-entropy](/docs/internals/anti-entropy), so in most situations
+[anti-entropy](/docs/architecture/anti-entropy), so in most situations
 everything will be in sync within a few seconds.
 
 | Method | Path                         | Produces           |
@@ -231,7 +231,7 @@ $ curl \
 ```
 
 The response has the same structure as the [service
-definition](/docs/agent/services) with one extra field `ContentHash` which
+definition](/docs/discovery/services) with one extra field `ContentHash` which
 contains the [hash-based blocking
 query](/api/features/blocking#hash-based-blocking-queries) hash for the result. The
 same hash is also present in `X-Consul-ContentHash`.
@@ -601,21 +601,21 @@ The corresponding CLI command is [`consul services register`](/commands/services
 
 ### Parameters
 
-Note that this endpoint, unlike most also [supports `snake_case`](/docs/agent/services#service-definition-parameter-case)
+Note that this endpoint, unlike most also [supports `snake_case`](/docs/discovery/services#service-definition-parameter-case)
 service definition keys for compatibility with the config file format.
 
 - `Name` `(string: <required>)` - Specifies the logical name of the service.
   Many service instances may share the same logical service name. We recommend using
   [valid DNS labels](https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_hostnames)
-  for [compatibility with external DNS](/docs/agent/services#service-and-tag-names-with-dns).
+  for [compatibility with external DNS](/docs/discovery/services#service-and-tag-names-with-dns).
 
 - `ID` `(string: "")` - Specifies a unique ID for this service. This must be
   unique per _agent_. This defaults to the `Name` parameter if not provided.
 
 - `Tags` `(array<string>: nil)` - Specifies a list of tags to assign to the
   service. These tags can be used for later filtering and are exposed via the APIs.
   We recommend using [valid DNS labels](https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_hostnames)
-  for [compatibility with external DNS](/docs/agent/services#service-and-tag-names-with-dns)
+  for [compatibility with external DNS](/docs/discovery/services#service-and-tag-names-with-dns)
 
 - `Address` `(string: "")` - Specifies the address of the service. If not
   provided, the agent's address is used as the address for the service during
@@ -639,9 +639,9 @@ service definition keys for compatibility with the config file format.
 - `Kind` `(string: "")` - The kind of service. Defaults to "" which is a
   typical Consul service. This value may also be "connect-proxy" for
   [Connect](/docs/connect) proxies representing another service,
-  "mesh-gateway" for instances of a [mesh gateway](/docs/connect/mesh-gateway),
-  "terminating-gateway" for instances of a [terminating gateway](/docs/connect/terminating-gateway),
-  or "ingress-gateway" for instances of a [ingress gateway](/docs/connect/ingress-gateway).
+  "mesh-gateway" for instances of a [mesh gateway](/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters),
+  "terminating-gateway" for instances of a [terminating gateway](/docs/connect/gateways/terminating-gateway),
+  or "ingress-gateway" for instances of a [ingress gateway](/docs/connect/gateways/ingress-gateway).
 
 - `Proxy` `(Proxy: nil)` - From 1.2.3 on, specifies the configuration for a
   Connect service proxy instance. This is only valid if `Kind` defines a proxy or gateway.
@@ -681,7 +681,7 @@ service definition keys for compatibility with the config file format.
   modifications would be lost.
 
 - `Weights` `(Weights: nil)` - Specifies weights for the service. Please see the
-  [service documentation](/docs/agent/services) for more information about
+  [service documentation](/docs/discovery/services) for more information about
   weights. If this field is not provided weights will default to
   `{"Passing": 1, "Warning": 1}`.
 
@@ -691,7 +691,7 @@ service definition keys for compatibility with the config file format.
   are independent of one another. Updating the tags for the service registered
   on one node is independent of the same service (by name) registered on
   another node. If `EnableTagOverride` is not specified the default value is
-  `false`. See [anti-entropy syncs](/docs/internals/anti-entropy) for
+  `false`. See [anti-entropy syncs](/docs/architecture/anti-entropy) for
   more info.
 
 #### Connect Structure

website/content/api-docs/catalog.mdx

@@ -17,7 +17,7 @@ API methods look similar.
 This endpoint is a low-level mechanism for registering or updating
 entries in the catalog. It is usually preferable to instead use the
 [agent endpoints](/api/agent) for registration as they are simpler and
-perform [anti-entropy](/docs/internals/anti-entropy).
+perform [anti-entropy](/docs/architecture/anti-entropy).
 
 | Method | Path                | Produces           |
 | ------ | ------------------- | ------------------ |
@@ -54,7 +54,7 @@ The table below shows this endpoint's support for
   provided, it will be defaulted to the value of the `Service.Service` property.
   Only one service with a given `ID` may be present per node. We recommend using
   [valid DNS labels](https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_hostnames)
-  for service definition names for [compatibility with external DNS](/docs/agent/services#service-and-tag-names-with-dns).
+  for service definition names for [compatibility with external DNS](/docs/discovery/services#service-and-tag-names-with-dns).
   The service `Tags`, `Address`, `Meta`, and `Port` fields are all optional. For more
   information about these fields and the implications of setting them,
   see the [Service - Agent API](/api/agent/service) page
@@ -74,7 +74,7 @@ The table below shows this endpoint's support for
   check. The `Status` must be one of `passing`, `warning`, or `critical`.
 
   The `Definition` field can be provided with details for a TCP or HTTP health
-  check. For more information, see the [Health Checks](/docs/agent/checks) page.
+  check. For more information, see the [Health Checks](/docs/discovery/checks) page.
 
   Multiple checks can be provided by replacing `Check` with `Checks` and
   sending an array of `Check` objects.
@@ -168,7 +168,7 @@ $ curl \
 This endpoint is a low-level mechanism for directly removing
 entries from the Catalog. It is usually preferable to instead use the
 [agent endpoints](/api/agent) for deregistration as they are simpler and
-perform [anti-entropy](/docs/internals/anti-entropy).
+perform [anti-entropy](/docs/architecture/anti-entropy).
 
 | Method | Path                  | Produces           |
 | ------ | --------------------- | ------------------ |

website/content/api-docs/coordinate.mdx

@@ -13,7 +13,7 @@ The `/coordinate` endpoints query for the network coordinates for nodes in the
 local datacenter as well as Consul servers in the local datacenter and remote
 datacenters.
 
-Please see the [Network Coordinates](/docs/internals/coordinates) internals
+Please see the [Network Coordinates](/docs/architecture/coordinates) internals
 guide for more information on how these coordinates are computed, and for
 details on how to perform calculations with them.
 

website/content/api-docs/discovery-chain.mdx

@@ -13,13 +13,13 @@ description: The /discovery-chain endpoints are for interacting with the discove
 high-level proxy integration APIs may obviate the need for this API over time.
 
 The `/discovery-chain` endpoint returns the compiled [discovery
-chain](/docs/internals/discovery-chain) for a service.
+chain](/docs/connect/l7-traffic/discovery-chain) for a service.
 
 This will fetch all related [configuration
 entries](/docs/agent/config-entries) and render them into a form suitable
 for use by a [connect proxy](/docs/connect/proxies) implementation. This
 is a key component of [L7 Traffic
-Management](/docs/connect/l7-traffic-management).
+Management](/docs/connect/l7-traffic).
 
 ## Read Compiled Discovery Chain
 
@@ -95,7 +95,7 @@ The table below shows this endpoint's support for
   parameter.
 
 - `OverrideMeshGateway` `(MeshGatewayConfig: <optional>)` - Overrides the final
-  [mesh gateway configuration](/docs/connect/mesh-gateway#connect-proxy-configuration)
+  [mesh gateway configuration](/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#connect-proxy-configuration)
   for this any service resolved in the compiled chain.
 
   This value comes from either the [proxy
@@ -111,7 +111,7 @@ The table below shows this endpoint's support for
 ### Sample Compilations
 
 Full documentation for the output fields is found on the [discovery chain
-internals](/docs/internals/discovery-chain#compileddiscoverychain)
+internals](/docs/connect/l7-traffic/discovery-chain#compileddiscoverychain)
 page.
 
 #### Multi-Datacenter Failover