Merge pull request #34675 from Srivaralakshmi/Tutorial-pipelines-1.5

Document tutorial updates for Pipelines1.5

Author: Preeticp

modules/op-about-triggers.adoc

@@ -12,7 +12,7 @@ For example, you define a CI/CD workflow using {pipelines-title} for your applic
 Triggers consist of the following main resources that work together to form a reusable, decoupled, and self-sustaining CI/CD system:
 
 --
-* The `TriggerBinding` resource validates events, extracts the fields from an event payload, and stores them as parameters.
+* The `TriggerBinding` resource extracts the fields from an event payload and stores them as parameters.
 +
 The following example shows a code snippet of the `TriggerBinding` resource, which extracts the Git repository information from the received event payload:
 +
@@ -90,13 +90,15 @@ spec:
 <1> The API version of the `TriggerTemplate` resource. In this example, `v1alpha1`.
 <2> Specifies the type of Kubernetes object. In this example, `TriggerTemplate`.
 <3> Unique name to identify the `TriggerTemplate` resource.
-<4> Parameters supplied by the `TriggerBinding` or `EventListerner` resources.
+<4> Parameters supplied by the `TriggerBinding` resource.
 <5> List of templates that specify the way resources must be created using the parameters received through the `TriggerBinding` or `EventListener` resources.
 
-* The `Trigger` resource connects the `TriggerBinding` and `TriggerTemplate` resources, and this `Trigger` resource is referenced in the `EventListener` specification.
+* The `Trigger` resource combines the `TriggerBinding` and `TriggerTemplate` resources, and optionally, the `interceptors` event processor. 
++
+Interceptors process all the events for a specific platform that runs before the `TriggerBinding` resource.  You can use interceptors to filter the payload, verify events, define and test trigger conditions, and implement other useful processing. Interceptors use secret for event verification. Once the event data passes through an interceptor, it then goes to the trigger before you pass the payload data to the trigger binding. You can also use an interceptor to modify the behavior of the associated trigger referenced in the `EventListener` specification.
 //image::op-triggers.png[]
 +
-The following example shows a code snippet of a `Trigger` resource, named `vote-trigger` that connects the `TriggerBinding` and `TriggerTemplate` resources.
+The following example shows a code snippet of a `Trigger` resource, named `vote-trigger` that connects the `TriggerBinding` and `TriggerTemplate` resources, and the `interceptors` event processor.
 +
 [source,yaml]
 ----
@@ -106,20 +108,41 @@ metadata:
   name: vote-trigger <3>
 spec:
   serviceAccountName: pipeline <4>
+  interceptors:
+    - ref:
+        name: "github" <5>
+      params: <6>
+        - name: "secretRef" 
+          value:
+            secretName: github-secret
+            secretKey: secretToken
+        - name: "eventTypes" 
+          value: ["push"]
   bindings:
-    - ref: vote-app <5>
-  template: <6>
+    - ref: vote-app <7>
+  template: <8>
      ref: vote-app
+...
+apiVersion: v1
+kind: Secret <9>
+metadata:
+  name: github-secret
+type: Opaque
+stringData:
+  secretToken: "1234567"
 ----
 +
 <1> The API version of the `Trigger` resource. In this example, `v1alpha1`.
 <2> Specifies the type of Kubernetes object. In this example, `Trigger`.
 <3> Unique name to identify the `Trigger` resource.
 <4> Service account name to be used.
-<5> Name of the `TriggerBinding` resource to be connected to the `TriggerTemplate` resource.
-<6> Name of the `TriggerTemplate` resource to be connected to the `TriggerBinding` resource.
+<5> Interceptor name to be referenced. In this example, `github`.
+<6> Desired parameters to be specified.
+<7> Name of the `TriggerBinding` resource to be connected to the `TriggerTemplate` resource.
+<8> Name of the `TriggerTemplate` resource to be connected to the `TriggerBinding` resource.
+<9> Secret to be used to verify events.
 
-* The `EventListener` resource provides an endpoint, or an event sink, that listens for incoming HTTP-based events with a JSON payload. It  extracts event parameters from each `TriggerBinding` resource, and then processes this data to create Kubernetes resources as specified by the corresponding `TriggerTemplate` resource. The `EventListener` resource also performs lightweight event processing or basic filtering on the payload using event `interceptors`, which identify the type of payload and optionally modify it. Currently, pipeline triggers support four types of interceptors: _Webhook Interceptors_, _GitHub Interceptors_, _GitLab Interceptors_, and _Common Expression Language (CEL) Interceptors_.
+* The `EventListener` resource provides an endpoint, or an event sink, that listens for incoming HTTP-based events with a JSON payload. It  extracts event parameters from each `TriggerBinding` resource, and then processes this data to create Kubernetes resources as specified by the corresponding `TriggerTemplate` resource. The `EventListener` resource also performs lightweight event processing or basic filtering on the payload using event `interceptors`, which identify the type of payload and optionally modify it. Currently, pipeline triggers support five types of interceptors: _Webhook Interceptors_, _GitHub Interceptors_, _GitLab Interceptors_, _Bitbucket Interceptors_, and _Common Expression Language (CEL) Interceptors_.
 +
 The following example shows an `EventListener` resource, which references the `Trigger` resource named `vote-trigger`.
 +

modules/op-installing-pipelines-operator-in-web-console.adoc

@@ -19,9 +19,9 @@ If you manually changed your existing installation, such as, changing the target
 The {pipelines-title} Operator now provides the option to choose the components that you want to install by specifying profiles as part of the `TektonConfig` CR. The `TektonConfig` CR is automatically installed when the Operator is installed.
 The supported profiles are:
 
-* Basic: This installs only Tekton pipelines.
-* Default: This installs Tekton pipeline and Tekton triggers.
-* All: This is the default profile used when the `TektonConfig` CR is installed. This profile installs all of the Tekton components: Tekton Pipelines, Tekton Triggers, Tekton Addons(which include `ClusterTasks`, `ClusterTriggerBindings`, `ConsoleCLIDownload`, `ConsoleQuickStart` and `ConsoleYAMLSample` resources).
+* Lite: This installs only Tekton Pipelines.
+* Basic: This installs Tekton Pipelines and Tekton Triggers.
+* All: This is the default profile used when the `TektonConfig` CR is installed. This profile installs all of the Tekton components: Tekton Pipelines, Tekton Triggers, Tekton Addons (which include `ClusterTasks`, `ClusterTriggerBindings`, `ConsoleCLIDownload`, `ConsoleQuickStart` and `ConsoleYAMLSample` resources).
 
 [discrete]
 .Procedure

modules/pipelines-document-attributes.adoc

@@ -9,4 +9,4 @@
 //
 :pipelines-title: Red Hat OpenShift Pipelines
 :pipelines-shortname: Pipelines
-:pipelines-ver: pipelines-1.4
+:pipelines-ver: pipelines-1.5