RHDHBUGS-2005 - Fixed broken link by replacing docs.redhat.com occurences by attributes - ocp

Signed-off-by: Fabrice Flore-Thébault <[email protected]>

Author: themr0c

modules/installation/proc-install-rhdh-helm-airgapped-full.adoc

@@ -12,7 +12,7 @@ If your network has access to the registry through a bastion host, you can use t
 ** You have installed the oc-mirror {openshift-cli} plugin, for more information see https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin].
 ** You have an account in https://developers.redhat.com/[{rhdeveloper-name}] portal.
 * You have set up your intermediary host.
-** Your host has access to the disconnected cluster and to the target mirror registry, for example, the {ocp-brand-name} image registry. For more information about exposing the {ocp-short} image registry, see https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/registry/index#securing-exposing-registry[Exposing the registry].
+** Your host has access to the disconnected cluster and to the target mirror registry, for example, the {ocp-brand-name} image registry. For more information about exposing the {ocp-short} image registry, see {ocp-docs-link}}/html-single/registry/index#securing-exposing-registry[Exposing the registry].
 ** You have installed the oc-mirror {openshift-cli} plugin, for more information see https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin].
 ** You have installed {ocp-brand-name} {ocp-version-min} or later.
 ** You have installed the {openshift-cli} on your workstation.

modules/installation/proc-install-rhdh-helm-airgapped-partial.adoc

@@ -8,7 +8,7 @@ If your network has access to the `registry.redhat.io` registry and the `charts.
 * You have installed {ocp-brand-name} {ocp-version-min} or later.
 * You have access to the `charts.openshift.io` Helm chart repository.
 * You have access to the `registry.redhat.io`.
-* You have access to a mirror registry that can be reached from the disconnected cluster, for example, the {ocp-short} image registry. For more information about exposing the {ocp-short} image registry, see https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/registry/index#securing-exposing-registry[Exposing the registry].
+* You have access to a mirror registry that can be reached from the disconnected cluster, for example, the {ocp-short} image registry. For more information about exposing the {ocp-short} image registry, see {ocp-docs-link}}/html-single/registry/index#securing-exposing-registry[Exposing the registry].
 * You are logged in to your target mirror registry and have permissions to push images to it. For more information, see link:https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-adding-registry-pull-secret_installing-mirroring-disconnected[Configuring credentials that allow images to be mirrored].
 * You have installed the {openshift-cli} on your workstation.
 * You have installed the oc-mirror {openshift-cli} plugin, for more information see https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin].
@@ -122,4 +122,4 @@ where:
 `<archive_file>` :: Specifies the name of the archive file containing the resources that you want to mirror, for example, `redhat-developer-hub-1.4.1.tgz`.
 
 `<your_namespace>` :: Specifies the namespace that you want to deploy the Helm chart to, for example, `{my-product-namespace}`.
---
+--

modules/installation/proc-install-rhdh-operator-airgapped-full.adoc

@@ -14,7 +14,7 @@ If your network has access to the registry through a bastion host, you can use t
 * You have installed the GNU `sed` command line text editor.
 * You have installed `umoci` CLI tool.
 * You have an active `oc registry`, `podman`, or `skopeo` session to the `registry.redhat.io` {company-name} Ecosystem Catalog. For more information, see link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
-* You have installed the `opm` CLI tool. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
+* You have installed the `opm` CLI tool. For more information, see link:{ocp-docs-link}/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
 
 .Procedure
 . Download the mirroring script to disk by running the following command:

modules/installation/proc-install-rhdh-operator-airgapped-partial.adoc

@@ -21,7 +21,7 @@ When connected to a {ocp-short} cluster, the helper script detects it and automa
 * You have installed `umoci` CLI tool.
 * You have an active `oc registry`, `podman`, or `skopeo` session to the `registry.redhat.io` {company-name} Ecosystem Catalog. For more information, see link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
 * You have an active `skopeo` session with administrative access to the target mirror registry. For more information, see link:https://github.com/containers/skopeo#authenticating-to-a-registry[Authenticating to a registry].
-* You have installed the `opm` CLI tool. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
+* You have installed the `opm` CLI tool. For more information, see link:{ocp-docs-link}/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
 * If you are using an {ocp-short} cluster, you have the following prerequisites:
 ** (Optional) You have installed the `oc-mirror` {ocp-short} CLI plugin if you want to use it to mirror images.
 * If you are using a supported Kubernetes cluster, you have the following prerequisites:

modules/observe/con-audit-log-config.adoc

@@ -6,10 +6,10 @@
 Use the {ocp-short} web console to configure the following {ocp-short} logging components to use audit logging for {product-short}:
 
 Logging deployment::
-Configure the logging environment, including both the CPU and memory limits for each logging component. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/logging/index#cluster-logging-memory[{ocp-brand-name} - Configuring your Logging deployment].
+Configure the logging environment, including both the CPU and memory limits for each logging component. For more information, see link:{ocp-docs-link}/html-single/logging/index#cluster-logging-memory[{ocp-brand-name} - Configuring your Logging deployment].
 
 Logging collector::
-Configure the `spec.collection` stanza in the `ClusterLogging` custom resource (CR) to use a supported modification to the log collector and collect logs from `STDOUT`. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/logging/index#cluster-logging-collector[{ocp-brand-name} - Configuring the logging collector].
+Configure the `spec.collection` stanza in the `ClusterLogging` custom resource (CR) to use a supported modification to the log collector and collect logs from `STDOUT`. For more information, see link:{ocp-docs-link}/html-single/logging/index#cluster-logging-collector[{ocp-brand-name} - Configuring the logging collector].
 
 Log forwarding::
-Send logs to specific endpoints inside and outside your {ocp-short} cluster by specifying a combination of outputs and pipelines in a `ClusterLogForwarder` CR. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/logging/index#cluster-logging-json-log-forwarding_cluster-logging-enabling-json-logging[{ocp-brand-name} - Enabling JSON log forwarding] and link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/logging/index#configuring-log-forwarding[{ocp-brand-name} - Configuring log forwarding].
+Send logs to specific endpoints inside and outside your {ocp-short} cluster by specifying a combination of outputs and pipelines in a `ClusterLogForwarder` CR. For more information, see link:{ocp-docs-link}/html-single/logging/index#cluster-logging-json-log-forwarding_cluster-logging-enabling-json-logging[{ocp-brand-name} - Enabling JSON log forwarding] and link:{ocp-docs-link}/html-single/logging/index#configuring-log-forwarding[{ocp-brand-name} - Configuring log forwarding].

modules/observe/proc-forward-audit-log-splunk.adoc

@@ -65,7 +65,7 @@ metadata:
   namespace: openshift-logging
 ----
 
-For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/logging/index#logging-create-clf_configuring-log-forwarding[Creating a log forwarder].
+For more information, see link:{ocp-docs-link}/html-single/logging/index#logging-create-clf_configuring-log-forwarding[Creating a log forwarder].
 --
 . Define the following `ClusterLogForwarder` configuration using OpenShift web console or OpenShift CLI:
 .. Specify the `log-collector` as `serviceAccount` in the YAML file:
@@ -94,7 +94,7 @@ inputs:
         maxRecordsPerSecond: 100
 ----
 
-For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/logging/index#cluster-logging-collector-log-forward-logs-from-application-pods_configuring-log-forwarding[Forwarding application logs from specific pods].
+For more information, see link:{ocp-docs-link}/html-single/logging/index#cluster-logging-collector-log-forward-logs-from-application-pods_configuring-log-forwarding[Forwarding application logs from specific pods].
 --
 .. Configure outputs to specify where the captured logs are sent. In this step, focus on the `splunk` type. You can either use `tls.insecureSkipVerify` option if the Splunk endpoint uses self-signed TLS certificates (not recommended) or provide the certificate chain using a Secret.
 +
@@ -116,7 +116,7 @@ outputs:
         maxRecordsPerSecond: 250
 ----
 
-For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/logging/index#logging-forward-splunk_configuring-log-forwarding[Forwarding logs to Splunk] in {ocp-short} documentation.
+For more information, see link:{ocp-docs-link}/html-single/logging/index#logging-forward-splunk_configuring-log-forwarding[Forwarding logs to Splunk] in {ocp-short} documentation.
 --
 .. Optional: Filter logs to include only audit logs:
 +
@@ -132,7 +132,7 @@ filters:
         - field: .message
           notMatches: isAuditEvent
 ----
-For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/logging/index#logging-content-filtering[Filtering logs by content] in {ocp-short} documentation.
+For more information, see link:{ocp-docs-link}/html-single/logging/index#logging-content-filtering[Filtering logs by content] in {ocp-short} documentation.
 --
 .. Configure pipelines to route logs from specific inputs to designated outputs. Use the names of the defined inputs and outputs to specify multiple `inputRefs` and `outputRefs` in each pipeline:
 +