Revert "Pipelines as Code documentation for Pipelines 1.9"

Author: rolfedh

_attributes/common-attributes.adoc

@@ -88,7 +88,7 @@ endif::[]
 //pipelines
 :pipelines-title: Red Hat OpenShift Pipelines
 :pipelines-shortname: Pipelines
-:pipelines-ver: pipelines-1.9
+:pipelines-ver: pipelines-1.8
 :tekton-chains: Tekton Chains
 :tekton-hub: Tekton Hub
 :pac: Pipelines as Code

cicd/pipelines/using-pipelines-as-code.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-// :FeatureName: Pipelines as Code
+:FeatureName: Pipelines as Code
 
 [role="_abstract"]
 With {pac}, cluster administrators and users with the required privileges can define pipeline templates as part of source code Git repositories. When triggered by a source code push or a pull request for the configured Git repository, the feature runs the pipeline and reports the status.   
@@ -30,107 +30,20 @@ include::modules/op-installing-pipelines-as-code-on-an-openshift-cluster.adoc[le
 
 include::modules/op-installing-pipelines-as-code-cli.adoc[leveloffset=+1]
 
-[id="using-pipelines-as-code-with-a-git-repository-hosting-service-provider"]
-== Using {pac} with a Git repository hosting service provider 
+include::modules/op-configuring-pipelines-as-code-for-a-git-repository-hosting-service-provider.adoc[leveloffset=+1]
 
-[role="_abstract"]
-After installing {pac}, cluster administrators can configure a Git repository hosting service provider. Currently, the following services are supported:
-
-* GitHub App
-* GitHub Webhook
-* GitLab
-* Bitbucket Server
-* Bitbucket Cloud
-
-[NOTE]
-====
-GitHub App is the recommended service for using with {pac}.
-====
-
-include::modules/op-using-pipelines-as-code-with-a-github-app.adoc[leveloffset=+1]
+include::modules/op-configuring-pipelines-as-code-for-a-github-app.adoc[leveloffset=+2]
 
 include::modules/op-creating-a-github-application-in-administrator-perspective.adoc[leveloffset=+2]
 
-include::modules/op-using-pipelines-as-code-with-github-webhook.adoc[leveloffset=+1]
-
-.Additional resources
-
-* link:https://docs.github.com/en/developers/webhooks-and-events/webhooks/creating-webhooks[GitHub Webhook documentation on GitHub]
-* link:https://docs.github.com/en/rest/guides/getting-started-with-the-checks-api[GitHub Check Runs documentation on GitHub]
-* link:https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token[Creating a personal access token on GitHub]
-* link:https://github.com/settings/tokens/new?description=pipelines-as-code-token&scopes=repo[Classic tokens with pre-filled permissions]
-
-include::modules/op-using-pipelines-as-code-with-gitlab.adoc[leveloffset=+1]
-
-.Additional resources
-
-* link:https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html[GitLab Webhook documentation on GitLab]
-
-include::modules/op-using-pipelines-as-code-with-bitbucket-cloud.adoc[leveloffset=+1]
-
-.Additional resources
-
-* link:https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/[Create app password on Bitbucket Cloud]
-* link:https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/#introducing-atlassian-account-id-and-nicknames[Introducing Altassian Account ID and Nicknames]
-
-include::modules/op-using-pipelines-as-code-with-bitbucket-server.adoc[leveloffset=+1]
-
-.Additional resources
-
-* link:https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html[Create personal tokens on Bitbucket Server]
-* link:https://support.atlassian.com/bitbucket-cloud/docs/manage-webhooks/#Create-webhooks[Create webhooks on Bitbucket server]
-
-include::modules/op-interfacing-pipelines-as-code-with-custom-certificates.adoc[leveloffset=+1]
-
-.Additional resources
-
-* xref:../../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object[Enabling the cluster-wide proxy]
-
-include::modules/op-using-repository-crd-with-pipelines-as-code.adoc[leveloffset=+1]
-
-include::modules/op-setting-concurrency-limits-in-repository-crd.adoc[leveloffset=+2]
-
-include::modules/op-using-pipelines-as-code-resolver.adoc[leveloffset=+1]
-
-include::modules/op-using-remote-task-annotations-with-pipelines-as-code.adoc[leveloffset=+2]
-
-include::modules/op-using-remote-pipeline-annotations-with-pipelines-as-code.adoc[leveloffset=+2]
-
-include::modules/op-creating-pipeline-run-using-pipelines-as-code.adoc[leveloffset=+1]
-
-.Additional resources
-
-* link:https://github.com/google/cel-spec/blob/master/doc/langdef.md[CEL language specification]
-
-include::modules/op-running-pipeline-run-using-pipelines-as-code.adoc[leveloffset=+1]
-
-include::modules/op-monitoring-pipeline-run-status-using-pipelines-as-code.adoc[leveloffset=+1]
-
-.Additional resources
-
-* link:https://github.com/chmouel/tekton-slack-task-status[An example task to send Slack messages on success or failure]
-* link:https://github.com/openshift-pipelines/pipelines-as-code/blob/7b41cc3f769af40a84b7ead41c6f037637e95070/.tekton/push.yaml[An example of a pipeline run with `finally` tasks triggered on push events]
-
-include::modules/op-using-private-repositories-with-pipelines-as-code.adoc[leveloffset=+1]
-
-.Additional resources
-
-* link:https://github.com/openshift-pipelines/pipelines-as-code/blob/main/test/testdata/pipelinerun_git_clone_private.yaml[An example of the `git-clone` task used for cloning private repositories]
-
-include::modules/op-cleaning-up-pipeline-run-using-pipelines-as-code.adoc[leveloffset=+1]
-
-include::modules/op-using-incoming-webhook-with-pipelines-as-code.adoc[leveloffset=+1]
+include::modules/op-pipelines-as-code-command-reference.adoc[leveloffset=+1]
 
 include::modules/op-customizing-pipelines-as-code-configuration.adoc[leveloffset=+1]
 
-include::modules/op-pipelines-as-code-command-reference.adoc[leveloffset=+1]
-
 [role="_additional-resources"]
 [id="additional-resources-pac"]
 == Additional resources
 
-* link:https://github.com/openshift-pipelines/pipelines-as-code/tree/main/.tekton[An example of the `.tekton/` directory in the Pipelines as Code repository]
-
 * xref:../../cicd/pipelines/installing-pipelines.adoc#installing-pipelines[Installing OpenShift Pipelines]
 
 * xref:../../cli_reference/tkn_cli/installing-tkn.adoc#installing-tkn[Installing tkn]

modules/op-cleaning-up-pipeline-run-using-pipelines-as-code.adoc

@@ -0,0 +1,22 @@
+// This module is included in the following assembly:
+//
+// *cicd/pipelines/using-pipelines-as-code.adoc
+
+:_content-type: REFERENCE
+[id="configuring-pipelines-as-code-for-a-git-repository-hosting-service-provider_{context}"]
+= Configuring {pac} for a Git repository hosting service provider 
+
+[role="_abstract"]
+After installing {pac}, cluster administrators can configure a Git repository hosting service provider. Currently, the following services are supported:
+
+* GitHub App
+* GitHub Webhook
+* GitLab
+* Bitbucket Server
+* Bitbucket Cloud
+
+[NOTE]
+====
+GitHub App is the recommended service for using Pipelines as Code.
+====
+

modules/op-configuring-pipelines-as-code-for-a-git-repository-hosting-service-provider.adoc

@@ -3,8 +3,8 @@
 // *cicd/pipelines/using-pipelines-as-code.adoc
 
 :_content-type: PROCEDURE
-[id="using-pipelines-as-code-with-a-github-app_{context}"]
-= Using {pac} with a GitHub App 
+[id="configuring-pipelines-as-code-for-a-github-app_{context}"]
+= Configuring {pac} for a GitHub App 
 
 [role="_abstract"]
 GitHub Apps act as a point of integration with {pipelines-title} and bring the advantage of Git-based workflows to OpenShift Pipelines. Cluster administrators can configure a single GitHub App for all cluster users. For GitHub Apps to work with Pipelines as Code, ensure that the webhook of the GitHub App points to the Pipelines as Code event listener route (or ingress endpoint) that listens for GitHub events.
@@ -40,6 +40,12 @@ To create and configure a GitHub App manually for {pac}, perform the following s
 * **GitHub Application Name**: `OpenShift Pipelines`
 * **Homepage URL**: OpenShift Console URL 
 * **Webhook URL**: The {pac} route or ingress URL. You can find it by running the command `echo https://$(oc get route -n openshift-pipelines pipelines-as-code-controller -o jsonpath='{.spec.host}')`.
++
+[NOTE]
+====
+If {pac} is installed without using the {pipelines-title} Operator, use the `pipelines-as-code` namespace instead of `openshift-pipelines`.
+====
++
 * **Webhook secret**: An arbitrary secret. You can generate a secret by executing the command `openssl rand -hex 20`.
 
 . Select the following **Repository permissions**:
@@ -78,14 +84,15 @@ To configure {pac} to access the newly created GitHub App, execute the following
 
 [source,terminal]
 ----
-$ oc -n openshift-pipelines create secret generic pipelines-as-code-secret \
-        --from-literal github-private-key="$(cat <PATH_PRIVATE_KEY>)" \ <1>
-        --from-literal github-application-id="<APP_ID>" \ <2>
-        --from-literal webhook.secret="<WEBHOOK_SECRET>" <3>
+$ oc -n openshift-pipelines create secret generic pipelines-as-code-secret \ <1>
+        --from-literal github-private-key="$(cat <PATH_PRIVATE_KEY>)" \ <2>
+        --from-literal github-application-id="<APP_ID>" \ <3>
+        --from-literal webhook.secret="<WEBHOOK_SECRET>" <4>
 ----
-<1> The path to the private key you downloaded while configuring the GitHub App.
-<2> The **App ID** of the GitHub App.
-<3> The webhook secret provided when you created the GitHub App. 
+<1> If {pac} is installed without using the {pipelines-title} Operator, use the `pipelines-as-code` namespace instead of `openshift-pipelines`.
+<2> The path to the private key you downloaded while configuring the GitHub App.
+<3> The **App ID** of the GitHub App.
+<4> The webhook secret provided when you created the GitHub App. 
 
 
 [NOTE]