-
Epic
-
Resolution: Done
-
Critical
-
None
-
paac-multiple-hub
-
12
-
False
-
None
-
False
-
To Do
-
RHDP-609 - Adoption of Pipelines As Code FY23
-
-
-
Epic Goal
-
- Customer have multiple hub instances and want to be able to use them from Paac.
Why is this important?
Scenarios
- Customer have their own hub for their set of private tasks
- 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)
- ...
Previous Work (Optional):
- …
Open questions::
- …
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
- is cloned by
-
RHDEVDOCS-5621 Support multiple tekton catalog hub in PaaC
- Open
- is documented by
-
RHDEVDOCS-5621 Support multiple tekton catalog hub in PaaC
- Open
- relates to
-
RFE-4049 Pipelines as Code: Specifying hub catalog source in a PipelineRun declaration
- Accepted