Loading...

XML

Word

Printable

Epic Name:
Migrate extensions catalog entities to overlay repo
Story Points:
8
Size:
M
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Parent Link:
RHDHPLAN-232Productization: Plugin Catalog / Extensions Marketplace (1.9)
Epic Status:
To Do
Feature Link:
RHDHPLAN-232 - Productization: Plugin Catalog / Extensions Marketplace (1.9)
Planning:

QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
Hierarchy Progress Bar:

67% To Do, 33% In Progress, 0% Done
Intelligence Requested:
Market:

Move extensions catalog entities to overlays

Copy content from rhdh to overlays repo
For package-level marketplace catalog entities, they would be generated. So in the overlay we should provide (in each related workspace) the minimal required, user-provided metadata to allow generating them, instead of just copying them verbatim from the RHDH repo.
Update https://gitlab.cee.redhat.com/rhidp/rhdh-plugin-catalog/-/blob/rhdh-1-rhel-9/upstream_repos.yml#L2-11 to not pull from rhdh repo

Switch to using helm chart and operator bundle to use the index object by default - see RHIDP-8934 and RHIDP-8935

Verify airgap installs work using catalog index and plugins from oci artifacts (not the embedded wrappers) - RHDHPLAN-253, RHIDP-8241
- both helm chart and operator bundle

If the above is all working in time for 1.9 FF, then we can also:

Delete catalog entities and dynamic-plugins.default.yaml from rhdh repo (in main for 1.9)

depends on

RHIDP-8241 RHDH Airgap preparation script - support using oci://my-quay/my-org/my-repo:tagOrSHA!some-plugin-reference-name

RHDHPLAN-253 Implement solution for mirroring OCI artifacts into an airgapped RHDH deployment

is cloned by

RHIDP-8937 Switch to oci URLs in dynamic-plugins.default.yaml and the catalog entities

is duplicated by

RHDHPLAN-236 Migrate manually created/maintained catalog-entities content to the overlays repo so it can be generated into the plugin catalog