-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Deploy Verdaccio on Janus Cluster
-
L
-
False
-
-
False
-
-
To Do
-
RHIDP-2595 - Maintain a fork of upstream backstage repos
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
-
Deploy Verdaccio on Janus Cluster
- Deploy Verdaccio on Janus Cluster to set up an internal but public NPM registry.
- see https://github.com/tumido/janus-dynamic-plugins-enablement-demo/blob/main/00_setup/crc.ipynb for some inspiration
Background/Feature Origin
- Internal requirement to manage npm package distribution.
Why is this important?
- Enables secure and controlled distribution of npm packages internally.
User Scenarios
- Developers managing npm packages in a secure environment.
- Operations team configuring and maintaining the registry.
Dependencies (internal and external)
- Verdaccio
- GitOps via ArgoCD
Acceptance Criteria
- Verdaccio successfully deployed on Janus Cluster.
- Both dev and prod instances are operational and accessible.
- deployment is done via the rhdh gitops repository
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>
