EPIC Goal

Consume the plugin catalog index from an OCI artifact or OCI image and populate the included data into the software catalog so that the user can see these data in the Extensions/Marketplace UI.

The OCI image should contain only Plugin, Package and maybe Collections yamls and should import just this catalog kinds.

The import should support multiple catalog indexes. (Maybe we can use the namespace catalog namespace feature to separate different catalog indexes?)

On option might be a new marketplace-backend configuration:

marketplace:
  catalog:
    # using object instead of array to make it easier for customers to add their own catalog
    # the key could be maybe used as namespace in the software catalog ???
    # what we have today (not this configuration but how it works)
    rhdh:
      namespace: rhdh # optional?
      cleanup: true # missing feature at the moment. delete catalog entities that are not containd anymore
      type: local-files
      local-files:
        path: /marketplace
        recursive: true

    # new
    rhdh-oci:
      cleanup: true # missing feature at the moment. delete catalog entities that are not containd anymore
      type: oci-image
      oci-image:
        ref: quay.io/rhdh/plugin-catalog-index:next
        # should work with the openshift registry as well and esp. in airgapped scenarios
        # auth?

    # customers:
    my-custom-catalog:
      type: oci-image
      oci-image:
        ref: quay.io/...
        auth: ...
      scheduler: 1h

Background/Feature Origin

With RHDHPLAN-232 we want migrate the catalog yaml files from the RHDH repository and container image into the rhdh-overlay repository and bundle them in one (or more) container images that contains just these metadata/index.

Why is this important?

Moving the catalog information from rhdh into rhdh-overlay allows more people (other teams and maybe the community) to make their plugins available in RHDH without changing our core.

Dependencies (internal and external)

1. An OCI artifact or OCI image that contains the metadata
2. An agreement how the data are saved / accessible.

Acceptance Criteria

1. We can use the OCI image or an OCI artifact (tbd) to load extensions catalog items
   1. Updates are fetched on startup
   2. Updates are optional fetched regularly
   3. Removed plugins or package metadata should be removed
2. It should work with an OCI registry that requires auth and with mirrowed OCI artifacts/images in OpenShift airgapped environments