-
Task
-
Resolution: Unresolved
-
Critical
-
None
-
1.3
-
None
-
False
-
-
False
-
-
The Notifications plugin was accepted into backstage/backstage as a core (static) plugin after the 1.2 release and so does not make sense as an example of a janus-idp dynamic plugin.
This section of the doc https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.2/html-single/configuring_plugins_in_red_hat_developer_hub/index#ref-example-dynamic-plugin-helm-installations is therefore outdated and needs to be reworked with a valid example.
In addition, it might be good to include newer versions of plugins - the two @dfatwork examples from dfestal are about a year old and 0.0.0 / 0.1 versions. Perhaps we could instead document how to install the RHAAP and Orchestrator plugins here?
For RHAAP: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.4/html/installing_ansible_plug-ins_for_red_hat_developer_hub/rhdh-install-ocp-helm_aap-plugin-rhdh-installing#rhdh-add-plugin-config_rhdh-ocp-required-installation
For Orchestrator:
- https://github.com/janus-idp/backstage-plugins/tree/main/plugins/orchestrator#setting-up-the-orchestrator-as-a-dynamic-plugin-in-a-helm-deployment
- https://www.parodos.dev/1.2/docs/installation/orchestrator/
- https://www.parodos.dev/blog/installation-on-existing-rhdh/
Alternatively, we could document some of the front/back/scaffolder plugins we have moved to https://github.com/backstage/community-plugins like ArgoCD and the relations processor scaffolder.