2.4. Configuring additional Pipelines as Code controllers to support additional GitHub apps

Procedure

1. In the TektonConfig custom resource, add the additionalPACControllers section to the platforms.openshift.pipelinesAsCode spec, as in the following example:

   Example additionalPACControllers section

   apiVersion: operator.tekton.dev/v1
   kind: TektonConfig
   metadata:
     name: config
   spec:
     platforms:
       openshift:
         pipelinesAsCode:
           additionalPACControllers:
             pac_controller_2:  

   1

   
               enable: true    

   2

   
               secretName: pac_secret_2  

   3

   
               settings: #  

   4

   
   # ...

   1

   The name of the controller. This name must be unique and not exceed 25 characters in length.

   2

   This parameter is optional. Set this parameter to true to enable the additional controller or to false to disable the additional controller. The default vaule is true.

   3

   Set this parameter to the name of a secret that you must create for the GitHub app.

   4

   This section is optional. In this section, you can set any Pipelines as Code settings for this controller if the settings must be different from the main Pipelines as Code controller.

2. Optional: If you want to use more than two GitHub apps, create additional sections under the pipelinesAsCode.additionalPACControllers spec to configure a Pipelines as Code controller for every GitHub instance. Use a unique name for every controller.