Bump xref cleanup (#389)

* Continue URL migration batch - update cloud-api references, fix deprecation policy header

* remaining updates

* These topics are migrated to Bump

* Missed edits

* Missed edits

Author: kbatuigas

modules/ROOT/nav.adoc

@@ -431,16 +431,16 @@
 *** xref:manage:schema-reg/programmable-push-filters.adoc[Programmable Push Filters]
 *** xref:manage:schema-reg/edit-topic-configuration.adoc[Edit Topic Configuration]
 ** xref:manage:api/index.adoc[Cloud API]
-*** xref:manage:api/cloud-api-quickstart.adoc[Cloud API Quickstart]
-*** xref:manage:api/cloud-api-overview.adoc[Cloud API Overview]
-*** xref:manage:api/cloud-api-authentication.adoc[Cloud API Authentication]
+*** link:/api/doc/cloud-controlplane/topic/topic-quickstart.adoc[Cloud API Quickstart]
+*** link:/api/doc/cloud-controlplane/topic/topic-cloud-api-overview.adoc[Cloud API Overview]
+*** link:/api/doc/cloud-controlplane/authentication.adoc[Cloud API Authentication]
 *** xref:manage:api/controlplane/index.adoc[Use the Control Plane API]
 **** xref:manage:api/cloud-byoc-controlplane-api.adoc[BYOC]
 **** xref:manage:api/cloud-dedicated-controlplane-api.adoc[Dedicated]
 **** xref:manage:api/cloud-serverless-controlplane-api.adoc[Serverless]
 *** xref:manage:api/cloud-dataplane-api.adoc[Use the Data Plane APIs]
-*** xref:manage:api/cloud-api-errors.adoc[Cloud API Errors and Status Codes]
-*** xref:manage:api/cloud-api-deprecation-policy.adoc[Cloud API Deprecation Policy]
+*** link:/api/doc/cloud-controlplane/topic/topic-error-and-status-codes.adoc[Cloud API Errors and Status Codes]
+*** link:/api/doc/cloud-controlplane/topic/topic-deprecation-policy.adoc[Cloud API Deprecation Policy]
 ** xref:manage:terraform-provider.adoc[]
 
 * xref:billing:index.adoc[Billing]
@@ -458,10 +458,10 @@
 *** xref:reference:tiers/byoc-tiers.adoc[]
 *** xref:reference:tiers/dedicated-tiers.adoc[]
 ** xref:reference:api-reference.adoc[]
-*** xref:api:ROOT:cloud-controlplane-api.adoc[]
-*** xref:api:ROOT:cloud-dataplane-api.adoc[]
-*** xref:api:ROOT:pandaproxy-rest.adoc[]
-*** xref:api:ROOT:pandaproxy-schema-registry.adoc[]
+*** link:/api/doc/cloud-controlplane/[Control Plane API]
+*** link:/api/doc/cloud-dataplane/[Data Plane APIs]
+*** link:/api/doc/http-proxy/[HTTP Proxy API]
+*** link:/api/doc/schema-registry/[Schema Registry API]
 ** xref:reference:properties/index.adoc[]
 *** xref:reference:properties/cluster-properties.adoc[]
 *** xref:reference:properties/object-storage-properties.adoc[]

modules/develop/pages/connect/configuration/resource-management.adoc

@@ -139,8 +139,8 @@ Cloud UI::
 Data Plane API::
 +
 --
-. xref:manage:api/cloud-api-quickstart.adoc#try-the-cloud-api[Authenticate and get the base URL] for the Data Plane API. 
-. Make a request to xref:api:ROOT:cloud-dataplane-api.adoc#get-/v1/redpanda-connect/pipelines[`GET /v1/redpanda-connect/pipelines`], which lists details of all pipelines on your cluster by ID. 
+. link:/api/doc/cloud-dataplane/topic/topic-quickstart[Authenticate and get the base URL] for the Data Plane API. 
+. Make a request to link:/api/doc/cloud-dataplane/operation/operation-redpandaconnectservice_listpipelines[`GET /v1/redpanda-connect/pipelines`], which lists details of all pipelines on your cluster by ID. 
 +
 * Memory (`memory_shares`) is displayed in megabytes. For example, `1` compute unit is `400M` or 400 MB.
 * CPU resources (`cpu_shares`) are displayed in milliCPU. For example, `1` compute unit is `100m` or 0.1 CPU.
@@ -167,9 +167,9 @@ Data Plane API::
 --
 You can only update CPU resources using the Data Plane API. For every 0.1 CPU that you allocate, Redpanda Cloud automatically reserves 400 MB of memory for the exclusive use of the pipeline.
 
-. xref:manage:api/cloud-api-quickstart.adoc#try-the-cloud-api[Authenticate and get the base URL] for the Data Plane API, if you haven't already.
-. Make a request to xref:api:ROOT:cloud-dataplane-api.adoc#get-/v1/redpanda-connect/pipelines/-id-[`GET /v1/redpanda-connect/pipelines/\{id}`], including the ID of the pipeline you want to update. You'll use the returned values in the next step.
-. Now make a request to xref:api:ROOT:cloud-dataplane-api.adoc#put-/v1/redpanda-connect/pipelines/-id-[`PUT /v1/redpanda-connect/pipelines/\{id}`], to update the pipeline resources:
+. link:/api/doc/cloud-dataplane/topic/topic-quickstart[Authenticate and get the base URL] for the Data Plane API, if you haven't already.
+. Make a request to link:/api/doc/cloud-dataplane/operation/operation-redpandaconnectservice_getpipeline[`GET /v1/redpanda-connect/pipelines/\{id}`], including the ID of the pipeline you want to update. You'll use the returned values in the next step.
+. Now make a request to link:/api/doc/cloud-dataplane/operation/operation-redpandaconnectservice_updatepipeline[`PUT /v1/redpanda-connect/pipelines/\{id}`], to update the pipeline resources:
 +
 * Reuse the values returned by your `GET` request to populate the request body. 
 * Replace the `cpu_shares` value with the resources you want to allocate, and enter any valid value for `memory_shares`.
@@ -194,6 +194,6 @@ curl -X PUT "https://<data-plane-api-url>/v1/redpanda-connect/pipelines/xxx..."
 ----
 +
 A successful response shows the updated resource allocations with the `cpu_shares` value returned in milliCPU.
-. Make a request to xref:api:ROOT:cloud-dataplane-api.adoc#get-/v1/redpanda-connect/pipelines[`GET /v1/redpanda-connect/pipelines`] to verify your pipeline resource updates.
+. Make a request to link:/api/doc/cloud-dataplane/operation/operation-redpandaconnectservice_listpipelines[`GET /v1/redpanda-connect/pipelines`] to verify your pipeline resource updates.
 --
 =====

modules/develop/pages/connect/configuration/secret-management.adoc

@@ -36,8 +36,8 @@ Data Plane API::
 --
 You must use a Base64-encoded secret.
 
-. xref:manage:api/cloud-api-quickstart.adoc#try-the-cloud-api[Authenticate and get the base URL] for the Data Plane API.
-. Make a request to xref:api:ROOT:cloud-dataplane-api.adoc#post-/v1/secrets[`POST /v1/secrets`].
+. link:/api/doc/cloud-dataplane/topic/topic-quickstart[Authenticate and get the base URL] for the Data Plane API.
+. Make a request to link:/api/doc/cloud-dataplane/operation/operation-secretservice_createsecret[`POST /v1/secrets`].
 
 [,bash]
 ----
@@ -87,8 +87,8 @@ Data Plane API::
 --
 You must use a Base64-encoded secret.
 
-. xref:manage:api/cloud-api-quickstart.adoc#try-the-cloud-api[Authenticate and get the base URL] for the Data Plane API.
-. Make a request to xref:api:ROOT:cloud-dataplane-api.adoc#put-/v1/secrets/-id-[`PUT /v1/secrets/\{id}`].
+. link:/api/doc/cloud-dataplane/topic/topic-quickstart[Authenticate and get the base URL] for the Data Plane API.
+. Make a request to link:/api/doc/cloud-dataplane/operation/operation-secretservice_updatesecret[`PUT /v1/secrets/\{id}`].
 +
 [,bash]
 ----
@@ -136,8 +136,8 @@ Data Plane API::
 +
 --
 
-. xref:manage:api/cloud-api-quickstart.adoc#try-the-cloud-api[Authenticate and get the base URL] for the Data Plane API.
-. Make a request to xref:api:ROOT:cloud-dataplane-api.adoc#delete-/v1/secrets/-id-[`DELETE /v1/secrets/\{id}`].
+. link:/api/doc/cloud-dataplane/topic/topic-quickstart[Authenticate and get the base URL] for the Data Plane API.
+. Make a request to link:/api/doc/cloud-dataplane/operation/operation-secretservice_deletesecret[`DELETE /v1/secrets/\{id}`].
 +
 [,bash]
 ----

modules/develop/pages/managed-connectors/disable-kc.adoc

@@ -1,7 +1,7 @@
 = Disable Kafka Connect
 :description: Learn how to disable Kafka Connect using the Cloud API.
 
-Kafka Connect is disabled by default on new clusters. If you previously enabled Kafka Connect on a cluster and want to disable it, you can use the xref:manage:api/cloud-api-overview.adoc[Cloud API]. 
+Kafka Connect is disabled by default on new clusters. If you previously enabled Kafka Connect on a cluster and want to disable it, you can use the link:/api/doc/cloud-controlplane/topic/topic-cloud-api-overview[Cloud API]. 
 
 NOTE: Redpanda Support does not manage or monitor Kafka Connect, but Support can enable the feature for your account.
 
@@ -30,13 +30,13 @@ If Kafka Connect is enabled, the response will show:
 == Prerequisites
 
 - You have the cluster ID of a cluster that has Kafka Connect enabled. 
-- You have a valid bearer token for the Cloud API. For details, see xref:manage:api/cloud-api-authentication.adoc[Authenticate to the API]. 
+- You have a valid bearer token for the Cloud API. For details, see link:/api/doc/cloud-controlplane/authentication[Authenticate to the API]. 
 
 IMPORTANT: Make sure to stop any active connectors gracefully before disabling Kafka Connect to avoid data loss or incomplete processing.
 
 == Disable Kafka Connect
 
-After you are authenticated to the Cloud API, make a xref:api:ROOT:cloud-controlplane-api.adoc#patch-/v1/clusters/-cluster.id-[`PATCH /v1/clusters/{cluster.id}`] request, replacing `{cluster.id}` with your actual cluster ID.
+After you are authenticated to the Cloud API, make a link:/api/doc/cloud-controlplane/operation/operation-clusterservice_updatecluster[`PATCH /v1/clusters/{cluster.id}`] request, replacing `{cluster.id}` with your actual cluster ID.
 
 [,bash]
 ----
@@ -46,7 +46,7 @@ curl -X PATCH "https://api.redpanda.com/v1/clusters/{cluster.id}" \
   -d '{"kafka_connect":{"enabled":false}}'
 ----
 
-The `PATCH` request returns the ID of a long-running operation. You can check the status of the operation by polling the xref:api:ROOT:cloud-controlplane-api.adoc#get-/v1/operations/-id-[`GET /operations/{id}`] endpoint:
+The `PATCH` request returns the ID of a long-running operation. You can check the status of the operation by polling the link:/api/doc/cloud-controlplane/operation/operation-operationservice_getoperation[`GET /operations/{id}`] endpoint:
 
 [,bash]
 ----

modules/get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc

@@ -28,7 +28,7 @@ For existing BYOVPC clusters, contact https://support.redpanda.com/hc/en-us/requ
 * Access to an AWS project in which you create your cluster.
 * Minimum permissions in that AWS project. For the actions required by the user who will create the cluster with `rpk cloud byoc aws apply`, see https://github.com/redpanda-data/cloud-examples/blob/main/customer-managed/aws/terraform/iam_rpk_user.tf[`iam_rpk_user.tf`^].
 * Each BYOVPC cluster requires one allocated Elastic IP (EIP) address in AWS.
-* Familiarity with the Redpanda Cloud API. For example, you should be familiar with how to use the Cloud API to xref:redpanda-cloud:manage:api/cloud-api-authentication.adoc[authenticate] and xref:redpanda-cloud:manage:api/cloud-byoc-controlplane-api.adoc[create a cluster].
+* Familiarity with the Redpanda Cloud API. For example, you should be familiar with how to use the Cloud API to link:/api/doc/cloud-controlplane/authentication[authenticate] and xref:redpanda-cloud:manage:api/cloud-byoc-controlplane-api.adoc[create a cluster].
 * https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli[Terraform^] version 1.8.5 or later.
 * https://jqlang.org/download/[jq^], which is used to parse JSON values from API responses.
 
@@ -139,7 +139,7 @@ export REDPANDA_RG_ID= #Retrieve the ID from the URL of the resource group when
 [TIP]
 ====
 
-* To get the Redpanda authentication credentials and resource group, follow the xref:manage:api/cloud-api-quickstart.adoc[].
+* To get the Redpanda authentication credentials, follow the link:/api/doc/cloud-controlplane/topic/authentication[Cloud API authentication guide]. You can link:/api/doc/cloud-controlplane/group/endpoint-resource-groups[use the API] to create a new resource group or use an existing one.
 * To see sample Terraform code of the expected provisioned resources, see the https://github.com/redpanda-data/cloud-examples/tree/main/customer-managed/aws[BYOVPC on AWS README^].
 ====
 
@@ -250,7 +250,7 @@ export CLOUD_STORAGE_BUCKET="$(terraform output -raw cloud_storage_bucket_arn)"
 export PERMISSIONS_BOUNDARY_POLICY="$(terraform output -raw permissions_boundary_policy_arn)"
 ```
 +
-TIP: See the full list of zones and tiers available with each provider in the xref:api:ROOT:cloud-controlplane-api.adoc#api-description[Control Plane API reference].
+TIP: See the full list of zones and tiers available with each provider in the link:/api/doc/cloud-controlplane/topic/topic-regions-and-usage-tiers[Control Plane API reference].
 
 . Define a JSON file called `redpanda-cluster.json` that includes cluster information: 
 +

modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc

@@ -27,7 +27,7 @@ See the code for the complete list of resources required to create and deploy Re
 
 * Access to an Azure subscription where you want to create your cluster
 * Knowledge of your internal VNet and subnet configuration
-* Permission to call the xref:manage:api/cloud-api-overview.adoc[Redpanda Cloud API]
+* Permission to call the link:/api/doc/cloud-controlplane/topic/topic-cloud-api-overview[Redpanda Cloud API]
 * Permission to create, modify, and delete the resources described by Terraform
 * https://developer.hashicorp.com/terraform/install[Terraform^] version 1.8.5 or later
 * https://jqlang.org/download/[jq^], which is used to parse JSON values from API responses
@@ -315,7 +315,7 @@ export BEARER_TOKEN=$(curl --request POST \
 --data audience=cloudv2-production.redpanda.cloud | jq -r '.access_token')
 ```
 
-TIP: To get the Redpanda authentication credentials, follow the xref:manage:api/cloud-api-quickstart.adoc[].
+TIP: To get the Redpanda authentication credentials, follow the link:/api/doc/cloud-controlplane/topic/authentication[authentication guide].
 
 == Create network
 
@@ -444,7 +444,7 @@ EOF
 ```
 ====
 +
-TIP: See the full list of zones and tiers available with each provider in the xref:api:ROOT:cloud-controlplane-api.adoc#api-description[Control Plane API reference].
+TIP: See the full list of zones and tiers available with each provider in the link:/api/doc/cloud-controlplane/topic/topic-regions-and-usage-tiers[Control Plane API reference].
 
 . Make a Cloud API call to create a Redpanda cluster and get the network ID from the response in JSON `.operation.metadata.network_id`.
 +

modules/get-started/pages/cluster-types/byoc/gcp/enable-rpcn-byovpc-gcp.adoc

@@ -87,7 +87,7 @@ gcloud iam service-accounts add-iam-policy-binding <redpanda_connect-gcp-sa-acco
 ```
 ====
 
-. Make a xref:api:ROOT:cloud-controlplane-api.adoc#patch-/v1/clusters/-cluster.id-[`PATCH /v1/clusters/\{cluster-id}`] request to update the cluster configuration.
+. Make a link:/api/doc/cloud-controlplane/operation/operation-clusterservice_updatecluster[`PATCH /v1/clusters/\{cluster-id}`] request to update the cluster configuration.
 +
 .Show request
 [%collapsible]

modules/get-started/pages/cluster-types/byoc/gcp/enable-secrets-byovpc-gcp.adoc

@@ -84,7 +84,7 @@ gcloud iam service-accounts add-iam-policy-binding <redpanda_operator-gcp-sa-acc
 ```
 ====
 
-. Make a xref:api:ROOT:cloud-controlplane-api.adoc#patch-/v1/clusters/-cluster.id-[`PATCH /v1/clusters/\{cluster-id}`] request to update the cluster configuration.
+. Make a link:/api/doc/cloud-controlplane/operation/operation-clusterservice_updatecluster[`PATCH /v1/clusters/\{cluster-id}`] request to update the cluster configuration.
 +
 .Show request
 [%collapsible]

modules/get-started/pages/cluster-types/byoc/remote-read-replicas.adoc

@@ -51,9 +51,9 @@ This should be done in the Terraform of the reader cluster.
 
 == Configure remote read replica
 
-Add or remove reader clusters to a source cluster in Redpanda Cloud with the xref:redpanda-cloud:manage:api/controlplane/index.adoc[Cloud Control Plane API]. For information on accessing the Cloud API, see xref:manage:api/cloud-api-authentication.adoc[].
+Add or remove reader clusters to a source cluster in Redpanda Cloud with the xref:redpanda-cloud:manage:api/controlplane/index.adoc[Cloud Control Plane API]. For information on accessing the Cloud API, see the link:/api/doc/cloud-controlplane/authentication[authentication guide].
 
-. To update your source cluster to add one or more reader cluster IDs, make a xref:api:ROOT:cloud-controlplane-api.adoc#patch-/v1/clusters/-cluster.id-[`PATCH /v1/clusters/{cluster.id}`] request. The full list of clusters is expected on every call. If an ID is removed from the list, it is removed as a reader cluster.
+. To update your source cluster to add one or more reader cluster IDs, make a link:/api/doc/cloud-controlplane/operation/operation-clusterservice_updatecluster[`PATCH /v1/clusters/{cluster.id}`] request. The full list of clusters is expected on every call. If an ID is removed from the list, it is removed as a reader cluster.
 +
 ```bash
 export SOURCE_CLUSTER_ID=.......
@@ -69,7 +69,7 @@ curl -X PATCH $API_HOST/v1/clusters/$SOURCE_CLUSTER_ID \
 EOF
 ```
 
-. Optional: To see the list of reader clusters on a given source cluster, make a xref:api:ROOT:cloud-controlplane-api.adoc#get-/v1/clusters/-id-[`GET /v1/clusters/\{id}`] request:
+. Optional: To see the list of reader clusters on a given source cluster, make a link:/api/doc/cloud-controlplane/operation/operation-clusterservice_getcluster[`GET /v1/clusters/\{id}`] request:
 +
 ```bash
 export SOURCE_CLUSTER_ID=.......