Problems:

When using the Pipeline Builder, developers are only able to install/upgrade tasks from the community Tekton Hub. When teams have their own set of curated tasks in a local Tekton Hub, they want the Pipeline Builder integrated with their local Tekton Hub.

Goals:

As an admin, when I have my own local Tekton Hub, I should be able to configure the Pipeline Builder so that it uses our own local Tekton Hub rather than the community version.

As a developer, when using the Pipeline Builder, it should be integrated with our own local Tekton Hub rather than the community version, so that I can search, install and upgrade our own set of curated tasks directly from the Dev Console where I create pipelines so that I don't have to switch contexts and leave OpenShift for discovering Tasks.

Why is it important?

To enable admins to provide access their own curated tasks from their local Tekton Hub for composing pipelines in pipeline builder

Acceptance criteria:

• Cluster admin can modify the default Tekton Hub API endpoint to point to their local Tekton Hub 

Dependencies (External/Internal):

• Tekton Hub API
• OpenShift Pipelines task library

Docs:

TBD