EPIC Goal

• Backend to provide metadata of available plugins in registry.

Background/Feature Origin

• Users need a way to browse and find plugins along with their basic metadata.

Why is this important?

• Facilitates easy discovery and usage of plugins by providing metadata and cataloging functionality, improving user experience.

User Scenarios

• Frontend can access a full catalog of available plugins with minimal metadata.
• Frontend can access detailed information for a specific plugin.
• Admins can configure multiple container registries to be browsed within app-config.yaml.

Dependencies (internal and external)

• Integration with container registries.
• Configuration dependencies in app-config.yaml.

Acceptance Criteria

• List full catalog of plugins with limited metadata.
• Provide details for a specific plugin.
• Enable configuration of multiple container registries in app-config.yaml.
• Implement logic to collect plugin metadata from container registries and cache the data, ensuring cache invalidation without DB storage.

Release Enablement/Demo - Provide necessary release enablement details and documents.
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>