Create a standalone dev environment for plugins that depend on catalog

tumido commented 1 year ago

While we already have a standalone dev environments backend plugins serving their own API endpoints, we're lacking a setup that would allow us to work against a Backstage catalog. Currently the only way how to see if entities are being properly discovered and ingested is to stand up packages/backstage and connect the plugin to it. This is not suitable if we want to isolate each plugin into separate dev environments.

~This currently blocks #324. If merged, we have no way to develop keycloak, 3scale, ocm, plugins.~

[x] Keycloak backend has a standalone dev environment - solved via https://github.com/janus-idp/backstage-plugins/pull/543
[x] #600
[x] #601
[x] #602
[x] #603

nickboldt commented 1 year ago

Relevant downstream issue: https://issues.redhat.com/browse/RHIDP-32

rhdh-bot commented 1 week ago

This issue has been closed due to the fact that the Janus community is being sunset.

For future plugin issues, please use https://github.com/backstage/community-plugins/issues

For future showcase issues, please use https://issues.redhat.com/browse/RHIDP

For more information on the sunset, see:

https://janus-idp.io/blog/2024/07/05/future-of-janus-community https://issues.redhat.com/browse/RHIDP-3690 https://issues.redhat.com/browse/RHIDP-1018

janus-idp / backstage-plugins

Create a standalone dev environment for plugins that depend on catalog #330