Preinstalled dynamic plugins
Red Hat Developer Hub is preinstalled with a selection of dynamic plugins.
The following 19 preinstalled dynamic plugins are enabled by default:
-
@backstage-community/plugin-analytics-provider-segment -
@backstage-community/plugin-scaffolder-backend-module-regex -
@backstage/plugin-org -
@backstage/plugin-techdocs -
@backstage/plugin-techdocs-backend -
@backstage/plugin-techdocs-module-addons-contrib -
@red-hat-developer-hub/backstage-plugin-adoption-insights -
@red-hat-developer-hub/backstage-plugin-adoption-insights-backend -
@red-hat-developer-hub/backstage-plugin-analytics-module-adoption-insights -
@red-hat-developer-hub/backstage-plugin-app-auth -
@red-hat-developer-hub/backstage-plugin-app-defaults -
@red-hat-developer-hub/backstage-plugin-app-integrations -
@red-hat-developer-hub/backstage-plugin-catalog-backend-module-extensions -
@red-hat-developer-hub/backstage-plugin-extensions -
@red-hat-developer-hub/backstage-plugin-extensions-backend -
@red-hat-developer-hub/backstage-plugin-global-header -
@red-hat-developer-hub/backstage-plugin-homepage -
@red-hat-developer-hub/backstage-plugin-homepage-backend -
@red-hat-developer-hub/backstage-plugin-quickstart
The dynamic plugins that require custom configuration are disabled by default.
Upon application startup, for each plugin that is disabled by default, the install-dynamic-plugins init container within the Developer Hub pod log displays a message similar to the following:
======= Skipping disabled dynamic plugin oci://quay.io/rhdh/backstage-plugin-auth-backend-module-github-provider@sha256:06e6f7de24d3f97ba4e980bd5aa8c8df467b2c3dc6c596635b5651a4d3d75e3c
To enable this plugin, add a package with the same name to the Helm chart and set the enabled field to true. For example:
global:
dynamic:
includes:
- dynamic-plugins.default.yaml
plugins:
- package: oci://quay.io/rhdh/backstage-plugin-auth-backend-module-github-provider@sha256:06e6f7de24d3f97ba4e980bd5aa8c8df467b2c3dc6c596635b5651a4d3d75e3c
enabled: true
The default configuration for a plugin is extracted from the
dynamic-plugins.default.yaml file, however, you can use a pluginConfig entry to override the default configuration.