Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-3219

Support multiple tekton catalog hub in PaaC

XMLWordPrintable

    • paac-multiple-hub
    • 12
    • False
    • None
    • False
    • To Do
    • RHDP-609 - Adoption of Pipelines As Code FY23
    • 0
    • 0% 0%
    • Hide

      This release introduces the ability for platform administrators to configure multiple hub endpoints within the Pipelines-as-Code Configmap, enabling greater flexibility in task selection. Pipelines as Code now supports customization of the catalog hub, allowing users to fetch tasks from different hub locations by specifying the desired catalog hub in their PipelineRun. This enhancement provides users with the capability to utilize tasks from multiple catalog hubs within the same PipelineRun, expanding the range of available resources.
      Show
      This release introduces the ability for platform administrators to configure multiple hub endpoints within the Pipelines-as-Code Configmap, enabling greater flexibility in task selection. Pipelines as Code now supports customization of the catalog hub, allowing users to fetch tasks from different hub locations by specifying the desired catalog hub in their PipelineRun. This enhancement provides users with the capability to utilize tasks from multiple catalog hubs within the same PipelineRun, expanding the range of available resources.

      Epic Goal

        • Customer have multiple hub instances and want to be able to use them from Paac.

      Why is this important?

      •  

      Scenarios

      1. Customer have their own hub for their set of private tasks
      2. User want to be able to fetch task from the private task and other task from the public one.

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …
      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

        1. image-2023-09-25-17-37-07-496.png
          image-2023-09-25-17-37-07-496.png
          35 kB
        2. image-2023-09-25-17-37-44-356.png
          image-2023-09-25-17-37-44-356.png
          34 kB

            cboudjna@redhat.com Chmouel Boudjnah
            cboudjna@redhat.com Chmouel Boudjnah
            Piyush Garg Piyush Garg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: