Feature Overview (aka. Goal Summary)

As a RHDH user, I want to be able to feed the Extensions cataliog with several source. Typically the RHDH supported plugins catalog, a catalog of all available community plugins, and possibly a catalog on in-house plugins developed by the RHDH customer.

Goals (aka. expected user outcomes)

The extensions plugin should be configurable to point to one or several plugin catalogs.

Plugin catalogs should contain only Plugin, Package and maybe Collections yamls, and should be made available at least as OCI images containing these metadata.

Requirements (aka. Acceptance Criteria):

1. It should be easy to configure additional catalogs through the RHDH app-config.
2. The resulting solution should be compatible with the air-gap scenario.

Out of Scope (Optional)

Customer Considerations (Optional)

Documentation Considerations