-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
Provide a Command Line Interface (CLI) for local development.
-
False
-
-
False
-
To Do
-
RHIDP-2534 - Plugin Marketplace
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
0% To Do, 0% In Progress, 100% Done
-
-
EPIC Goal
Provide a Command Line Interface (CLI) for local development.
Background/Feature Origin
- Developers need a way to bundle and publish plugins for RHDH easily.
- A CLI tool will streamline the development process.
Why is this important?
- Simplifies the development workflow for plugin developers.
- Ensures consistency in plugin packaging and publishing.
User Scenarios
- As a developer, I want to convert a local plugin source to a dynamic plugin.
- As a developer, I want to build a container image containing multiple plugins and push it to a registry.
Dependencies (internal and external)
- Dependencies on container registries like Docker Hub or Quay.io.
Acceptance Criteria
- CLI can bundle a local plugin source into a dynamic plugin.
- CLI can build a container image containing one or multiple plugins.
- CLI can push the built container image to a specified registry.
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>
- is cloned by
-
RHIDP-2816 Backend to provide metadata of available plugins in registry.
- New
- is depended on by
-
RHIDP-2740 Automate the process of building and pushing plugins to the registry.
- Closed