Finalize the dynamic backend plugin support in upstream backstage
davidfestal opened this issue · comments
David Festal commented
Goal
Finalize the dynamic backend plugin support in upstream backstage.
Since in upstream Backstage there is not plan to promote dynamic plugins on the old backend, ideally this EPIC would depend on EPIC #834.
Acceptance criteria
- Have the showcase support dynamic backend plugins by simply importing upstream backstage packages, without specific showcase logic or workarounds.
Requirements
- Test plan
- Documentation
Issues in Epic
- Make the Janus CLI work on backstage upstream plugins
- Support new backend system default exports in the upstream
backend-plugin-manager
(PR backstage/backstage#21612) - Fix in upstream the limitations encountered on the Showcase and fixed through workarounds
- Followups on the initial RFC PR, to make the package public (it's private for now), and have it published in NPMJS in the
@backstage
organization:- Better follow Backstage API Design style guidelines (PR: backstage/backstage#21764)
- Rename package to a more precise name
- Wait for a new Backstage release with the renamed
backstage -plugin-manager
published to NPM. - Update the Showcase to bump the backstage dependencies to this backstage release and use the lastest, renamed dynamic plugins service package.
Notes
Additional context
Add any other context or screenshots about the epic here.