Merge pull request #87951 from mramendi/RHDEVDOCS-6363

xenolinux · web-flow · commit 37b1766f4f25 · 2025-02-07T10:39:05.000+05:30
RHDEVDOCS 6363 fix broken links - Pipelines
diff --git a/create/creating-applications-with-cicd-pipelines.adoc b/create/creating-applications-with-cicd-pipelines.adoc
@@ -47,7 +47,7 @@ include::modules/op-mirroring-images-to-run-pipelines-in-restricted-environment.
 
 * link:https://docs.openshift.com/container-platform/latest/openshift_images/configuring-samples-operator.html#samples-operator-restricted-network-install[Configuring Samples Operator for a restricted cluster]
 
-* link:https://docs.openshift.com/container-platform/latest/installing/disconnected_install/installing-mirroring-installation-images.html#installation-about-mirror-registry_installing-mirroring-installation-images[Creating a cluster with a mirrored registry]
+* link:https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/index.html[About disconnected installation mirroring]
 
 include::modules/op-running-a-pipeline.adoc[leveloffset=+1]
 
@@ -72,7 +72,7 @@ include::modules/op-enabling-monitoring-of-event-listeners-for-triggers-for-user
 [id="additional-resources-enabling-monitoring_{context}"]
 .Additional resources
 
-* link:https://docs.openshift.com/container-platform/latest/monitoring/enabling-monitoring-for-user-defined-projects.html[Enabling monitoring for user-defined projects]
+* link:https://docs.openshift.com/container-platform/latest/observability/monitoring/enabling-monitoring-for-user-defined-projects.html[Enabling monitoring for user-defined projects]
 
 include::modules/op-configuring-pull-request-capabilities-in-GitHub-interceptor.adoc[leveloffset=+1]
 
diff --git a/install_config/installing-pipelines.adoc b/install_config/installing-pipelines.adoc
@@ -16,7 +16,7 @@ This guide walks cluster administrators through the process of installing the {p
 * You have access to an {OCP} cluster using an account with `cluster-admin` permissions.
 * You have installed `oc` CLI.
 * You have installed xref:../tkn_cli/installing-tkn.adoc#installing-tkn[{pipelines-shortname} (`tkn`) CLI] on your local system.
-* Your cluster has the link:https://docs.openshift.com/container-platform/latest/installing/cluster-capabilities.html#marketplace-operator_cluster-capabilities[Marketplace capability] enabled or the Red Hat Operator catalog source configured manually.
+* Your cluster has the link:https://docs.openshift.com/container-platform/latest/installing/overview/cluster-capabilities.html#marketplace-operator_cluster-capabilities[Marketplace capability] enabled or the Red{nbsp}Hat Operator catalog source configured manually.
 
 [NOTE]
 ====
@@ -50,4 +50,4 @@ include::modules/op-pipelines-operator-in-restricted-environment.adoc[leveloffse
 
 ** link:https://docs.openshift.com/container-platform/latest/openshift_images/configuring-samples-operator.html#samples-operator-restricted-network-install[Configuring Samples Operator for a restricted cluster]
 
-** link:https://docs.openshift.com/container-platform/latest/installing/disconnected_install/installing-mirroring-installation-images.html#installation-about-mirror-registry_installing-mirroring-installation-images[Creating a cluster with a mirrored registry]
+** link:https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/index.html[About disconnected installation mirroring]
diff --git a/modules/op-chains-signing-secrets-cosign.adoc b/modules/op-chains-signing-secrets-cosign.adoc
@@ -10,7 +10,7 @@ You can use the `cosign` signing scheme with {tekton-chains} using the `cosign`
 
 .Prerequisites
 
-* You installed the link:https://docs.sigstore.dev/cosign/installation/[cosign] tool.
+* You installed the Cosign tool. For information about installing the Cosign tool, see the link:https://docs.sigstore.dev/cosign/system_config/installation/[Sigstore documentation for Cosign].
 
 .Procedure
 
diff --git a/modules/op-creating-and-verifying-task-run-signatures-without-any-additional-authentication.adoc b/modules/op-creating-and-verifying-task-run-signatures-without-any-additional-authentication.adoc
@@ -19,7 +19,7 @@ Ensure that the following components are installed on the cluster:
 
 * {pipelines-title} Operator
 * {tekton-chains}
-* link:https://docs.sigstore.dev/cosign/installation/[Cosign]
+* link:https://docs.sigstore.dev/cosign/system_config/installation/[Cosign]
 
 .Procedure
 
diff --git a/modules/op-creating-repository-cr.adoc b/modules/op-creating-repository-cr.adoc
@@ -21,7 +21,7 @@ EOF
 ----
 <1> `my-pipeline-ci` is the target namespace.
 
-Whenever there is an event coming from the URL such as `https://github.com/<repository>/<project>`, {pac} matches it and then starts checking out the content of the `<repository>/<project>` repository for pipeline run to match the content in the `.tekton/` directory.
+Whenever there is an event coming from the URL such as `\https://github.com/<repository>/<project>`, {pac} matches it and then starts checking out the content of the `<repository>/<project>` repository for the pipeline run to match the content in the `.tekton/` directory.
 
 [NOTE]
 ====
diff --git a/modules/op-setting-up-openshift-pipelines-to-download-or-view-sboms.adoc b/modules/op-setting-up-openshift-pipelines-to-download-or-view-sboms.adoc
@@ -72,8 +72,8 @@ spec:
 ...
 spec:
   tasks:
-    - name: sbom-task  
-      taskRef: 
+    - name: sbom-task
+      taskRef:
         name: sbom-task # <1>
   results:
     - name: IMAGE_URL  # <2>
@@ -109,7 +109,7 @@ spec:
 
 .Prerequisites
 
-* You have installed the link:https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/how-to-guides/Secure-your-supply-chain/proc_inspect_sbom/[Cosign] CLI tool.
+* You have installed the Cosign CLI tool. For information about installing the Cosign tool, see the link:https://docs.sigstore.dev/cosign/system_config/installation/[Sigstore documentation for Cosign].
 
 * You have set up {pipelines-shortname} to download or view SBOMs.
 
@@ -182,4 +182,4 @@ This information helps you verify that individual libraries are safely-sourced,
                     "name": "syft:package:foundBy",
                     "value": "python-package-cataloger"
                     ...
-----
+----
diff --git a/modules/op-supported-parameters-tekton-chains-configuration.adoc b/modules/op-supported-parameters-tekton-chains-configuration.adoc
@@ -109,7 +109,7 @@ Cluster administrators can use various supported parameter keys and values to co
 
 | `signers.kms.kmsref`
 | The URI reference to a KMS service to use in `kms` signers.
-| Supported schemes: `gcpkms://`, `awskms://`, `azurekms://`, `hashivault://`. See link:https://docs.sigstore.dev/cosign/kms_support[KMS Support] in the Sigstore documentation for more details.
+| Supported schemes: `gcpkms://`, `awskms://`, `azurekms://`, `hashivault://`. See link:https://docs.sigstore.dev/cosign/key_management/overview/#providers[Providers] in the Sigstore documentation for more details.
 |
 |===
 
@@ -139,8 +139,8 @@ Cluster administrators can use various supported parameter keys and values to co
 
 | `builddefinition.buildtype`
 | The build type for in-toto attestation. When this parameter is `\https://tekton.dev/chains/v2/slsa`, {tekton-chains} records in-toto attestations in strict conformance with the SLSA v1.0 specification. When this parameter is `\https://tekton.dev/chains/v2/slsa-tekton`, {tekton-chains} records in-toto attestations with additional information, such as the labels and annotations in each `TaskRun` and `PipelineRun` object, and also adds each task in a `PipelineRun` object under `resolvedDependencies`.
-| `https://tekton.dev/chains/v2/slsa`,`https://tekton.dev/chains/v2/slsa-tekton`
-| `https://tekton.dev/chains/v2/slsa`
+| `\https://tekton.dev/chains/v2/slsa`,`\https://tekton.dev/chains/v2/slsa-tekton`
+| `\https://tekton.dev/chains/v2/slsa`
 
 
 |===
diff --git a/modules/op-using-remote-task-annotations-with-pipelines-as-code.adoc b/modules/op-using-remote-task-annotations-with-pipelines-as-code.adoc
@@ -76,9 +76,9 @@ To include remote tasks, refer to the following examples of annotation:
 ====
 * If you use GitHub and the remote task URL uses the same host as the `Repository` custom resource definition (CRD), {pac} uses the GitHub token and fetches the URL using the GitHub API.
 +
-For example, if you have a repository URL similar to `https://github.com/<organization>/<repository>` and the remote HTTP URL references a GitHub blob similar to `https://github.com/<organization>/<repository>/blob/<mainbranch>/<path>/<file>`, {pac} fetches the task definition files from that private repository with the GitHub App token.
+For example, if you have a repository URL similar to `\https://github.com/<organization>/<repository>` and the remote HTTP URL references a GitHub blob similar to `\https://github.com/<organization>/<repository>/blob/<mainbranch>/<path>/<file>`, {pac} fetches the task definition files from that private repository with the GitHub App token.
 +
-When you work on a public GitHub repository, {pac} acts similarly for a GitHub raw URL such as `https://raw.githubusercontent.com/<organization>/<repository>/<mainbranch>/<path>/<file>`.
+When you work on a public GitHub repository, {pac} acts similarly for a GitHub raw URL such as `\https://raw.githubusercontent.com/<organization>/<repository>/<mainbranch>/<path>/<file>`.
 
 
 * GitHub App tokens are scoped to the owner or organization where the repository is located. When you use the GitHub webhook method, you can fetch any private or public repository on any organization where the personal token is allowed.
diff --git a/modules/op-using-tekton-chains-to-sign-and-verify-image-and-provenance.adoc b/modules/op-using-tekton-chains-to-sign-and-verify-image-and-provenance.adoc
@@ -15,12 +15,12 @@ Cluster administrators can use {tekton-chains} to sign and verify images and pro
 * Verify the signed image and the signed provenance.
 
 .Prerequisites
-Ensure that the following are installed on the cluster:
+Ensure that the following tools are installed on the cluster:
 
 * {pipelines-title} Operator
 * {tekton-chains}
-* link:https://docs.sigstore.dev/cosign/installation/[Cosign]
-* link:https://docs.sigstore.dev/rekor/installation/[Rekor]
+* link:https://docs.sigstore.dev/cosign/system_config/installation/[Cosign]
+* link:https://docs.sigstore.dev/logging/installation/[Rekor]
 * link:https://stedolan.github.io/jq/[jq]
 
 .Procedure
diff --git a/records/viewing-pipeline-logs-using-the-openshift-logging-operator.adoc b/records/viewing-pipeline-logs-using-the-openshift-logging-operator.adoc
@@ -23,10 +23,15 @@ Before trying to view pipeline logs in a Kibana dashboard, ensure the following:
 
 include::modules/op-viewing-pipeline-logs-in-kibana.adoc[leveloffset=+1]
 
+////
+COMMENTED OUT BECAUSE THE LINKS ARE INVALID FOR NOW
+
 [role="_additional-resources"]
 [id="additional-resources_viewing-pipeline-logs-using-the-openshift-logging-operator"]
 == Additional resources
 
 * link:https://docs.openshift.com/container-platform/latest/logging/cluster-logging-deploying.html[Installing OpenShift Logging]
 * link:https://docs.openshift.com/container-platform/latest/logging/viewing-resource-logs.html[Viewing logs for a resource]
 * link:https://docs.openshift.com/container-platform/latest/logging/cluster-logging-visualizer.html[Viewing cluster logs by using Kibana]
+
+////

Original file line number	Diff line number	Diff line change
`@@ -76,9 +76,9 @@ To include remote tasks, refer to the following examples of annotation:`
`76`	`76`	`====`
`77`	`77`	* If you use GitHub and the remote task URL uses the same host as the `Repository` custom resource definition (CRD), {pac} uses the GitHub token and fetches the URL using the GitHub API.
`78`	`78`	`+`
`79`		-For example, if you have a repository URL similar to `https://github.com/<organization>/<repository>` and the remote HTTP URL references a GitHub blob similar to `https://github.com/<organization>/<repository>/blob/<mainbranch>/<path>/<file>`, {pac} fetches the task definition files from that private repository with the GitHub App token.
	`79`	+For example, if you have a repository URL similar to `\https://github.com/<organization>/<repository>` and the remote HTTP URL references a GitHub blob similar to `\https://github.com/<organization>/<repository>/blob/<mainbranch>/<path>/<file>`, {pac} fetches the task definition files from that private repository with the GitHub App token.
`80`	`80`	`+`
`81`		-When you work on a public GitHub repository, {pac} acts similarly for a GitHub raw URL such as `https://raw.githubusercontent.com/<organization>/<repository>/<mainbranch>/<path>/<file>`.
	`81`	+When you work on a public GitHub repository, {pac} acts similarly for a GitHub raw URL such as `\https://raw.githubusercontent.com/<organization>/<repository>/<mainbranch>/<path>/<file>`.
`82`	`82`
`83`	`83`
`84`	`84`	`* GitHub App tokens are scoped to the owner or organization where the repository is located. When you use the GitHub webhook method, you can fetch any private or public repository on any organization where the personal token is allowed.`