Dynamic plugins reference
Red Hat Developer Hub is preinstalled with a selection of dynamic plugins that you can enable and configure to extend Developer Hub functionality
Abstract
Red Hat Developer Hub (RHDH) is preinstalled with a selection of dynamic plugins that users can enable and configure to extend RHDH functionality.
The dynamic plugin support is based on the backend plugin manager package, which is a service that scans a configured root directory (dynamicPlugins.rootDirectory in the app config) for dynamic plugin packages and loads them dynamically.
You can use the dynamic plugins that come preinstalled with Red Hat Developer Hub or install external dynamic plugins from a public NPM registry.
1. Preinstalled dynamic plugins
Red Hat Developer Hub is preinstalled with a selection of dynamic plugins.
The following 15 preinstalled dynamic plugins are enabled by default:
-
@backstage-community/plugin-analytics-provider-segment -
@backstage-community/plugin-scaffolder-backend-module-regex -
@backstage/plugin-techdocs-backend -
@backstage/plugin-techdocs-module-addons-contrib -
@backstage/plugin-techdocs -
@red-hat-developer-hub/backstage-plugin-adoption-insights-backend -
@red-hat-developer-hub/backstage-plugin-adoption-insights -
@red-hat-developer-hub/backstage-plugin-analytics-module-adoption-insights -
@red-hat-developer-hub/backstage-plugin-catalog-backend-module-extensions -
@red-hat-developer-hub/backstage-plugin-dynamic-home-page -
@red-hat-developer-hub/backstage-plugin-extensions-backend -
@red-hat-developer-hub/backstage-plugin-extensions -
@red-hat-developer-hub/backstage-plugin-global-floating-action-button -
@red-hat-developer-hub/backstage-plugin-global-header -
@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 ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic
To enable this plugin, add a package with the same name to the Helm chart and change the value in the disabled field to false. For example:
global:
dynamic:
includes:
- dynamic-plugins.default.yaml
plugins:
- package: ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic
disabled: false
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.
2. Red Hat supported plugins
Red Hat provides full support for the following 33 dynamic plugins.
| Name | Plugin | Version | Path and required variables |
|---|---|---|---|
|
Adoption Insights |
0.8.1 |
| |
|
Adoption Insights |
|
0.8.1 |
|
|
Analytics Module Adoption Insights |
|
0.8.1 |
|
|
Analytics Provider Segment |
1.27.0 |
| |
|
Dynamic Home Page |
1.13.1 |
| |
|
GitHub Org |
0.3.20 |
| |
|
GitHub |
0.13.0 |
| |
|
GitHub |
0.9.7 |
| |
|
GitLab Org |
0.2.19 |
| |
|
GitLab |
0.8.1 |
| |
|
Global Floating Action Button |
|
1.9.1 |
|
|
Global Header |
1.21.4 |
| |
|
Http Request |
5.6.0 |
| |
|
Keycloak |
3.19.2 |
| |
|
Kubernetes |
0.21.2 |
| |
|
Kubernetes |
|
2.17.1 |
|
|
Ldap |
0.12.3 |
| |
|
MS Graph |
0.9.1 |
| |
|
Orchestrator Backend Module Loki |
|
1.2.5 |
|
|
Orchestrator Form Widgets |
|
1.10.6 |
|
|
Orchestrator |
5.7.10 |
| |
|
Orchestrator |
|
8.9.4 |
|
|
Orchestrator |
|
1.5.4 |
|
|
Quickstart |
1.9.3 |
| |
|
RBAC |
1.52.4 |
| |
|
Regex |
2.15.1 |
| |
|
Signals |
0.3.13 |
| |
|
Tech Radar |
1.17.0 |
| |
|
Tech Radar |
1.16.0 |
| |
|
TechDocs Module Addons Contrib |
1.1.34 |
| |
|
TechDocs |
1.17.2 |
| |
|
TechDocs |
2.1.6 |
| |
|
Topology |
2.12.2 |
|
- For more information about configuring KeyCloak, see Configuring dynamic plugins.
- For more information about configuring TechDocs, see Configuring TechDocs.
3. Red Hat Technology Preview plugins
Red Hat provides Technology Preview support for the following 15 plugins.
These features are for Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information on Red Hat Technology Preview features, see Technology Preview Features Scope.
| Name | Plugin | Version | Path and required variables |
|---|---|---|---|
|
ACR |
1.24.1 |
| |
|
Bulk Import |
7.3.2 |
| |
|
Bulk Import |
7.3.2 |
| |
|
Events Backend Module GitHub |
0.4.10 |
| |
|
Extensions |
0.17.1 |
| |
|
Extensions |
|
0.17.1 |
|
|
Extensions |
0.17.1 |
| |
|
GitLab |
0.11.4 |
| |
|
Kubernetes |
0.12.17 |
| |
|
Notifications |
0.5.15 |
| |
|
Notifications |
0.3.19 |
| |
|
Notifications |
0.6.3 |
| |
|
Pingidentity |
|
0.11.1 |
|
|
Scaffolder Relation Processor |
|
2.14.2 |
|
|
Signals |
0.0.29 |
|
4. Red Hat community supported plugins
Red Hat provides community support for the following 44 dynamic plugins in ghcr.io.
Replace <tag> with the version tag corresponding to your Developer Hub version. See Determining Tag Values
| Name | Version | Path |
|---|---|---|
|
3Scale |
3.13.0 |
|
|
ArgoCD Backend |
1.4.0 |
|
|
Azure DevOps Backend |
0.27.0 |
|
|
Catalog Backend Module Azure DevOps Annotator Processor |
0.18.0 |
|
|
Catalog Backend Module Bitbucket Cloud |
0.5.9 |
|
|
Catalog Backend Module Bitbucket Server |
0.5.9 |
|
|
Datadog |
2.7.2 |
|
|
Dynatrace |
10.17.0 |
|
|
GitHub Actions |
0.22.0 |
|
|
GitHub Deployments |
0.18.0 |
|
|
GitHub Discussions |
0.10.0 |
|
|
GitHub Discussions Search Backend Module |
0.11.0 |
|
|
GitHub Insights |
3.5.0 |
|
|
GitHub Issues |
0.21.0 |
|
|
GitHub Pull Requests |
3.7.0 |
|
|
GitHub Pull Requests Board |
0.16.0 |
|
|
GitLab Backend |
7.0.1 |
|
|
JFrog Artifactory |
1.28.0 |
|
|
Jenkins Backend |
0.27.0 |
|
|
Jenkins Scaffolder Backend Module |
0.20.0 |
|
|
Jira |
2.14.0 |
|
|
Lighthouse Backend |
0.21.0 |
|
|
Nexus Repository Manager |
1.23.2 |
|
|
PagerDuty Backend |
0.12.0 |
|
|
PagerDuty Entity Processor |
0.3.10 |
|
|
PagerDuty Scaffolder Actions |
0.2.9 |
|
|
Quay Backend |
1.14.0 |
|
|
Roadie ArgoCD Backend |
4.8.0 |
|
|
Scaffolder Backend ArgoCD |
1.8.1 |
|
|
Scaffolder Backend Module AWS |
2.8.2 |
|
|
Scaffolder Backend Module Azure |
0.2.19 |
|
|
Scaffolder Backend Module Azure DevOps |
0.23.0 |
|
|
Scaffolder Backend Module Bitbucket Cloud |
0.3.4 |
|
|
Scaffolder Backend Module Bitbucket Server |
0.2.19 |
|
|
Scaffolder Backend Module DotNet |
0.13.0 |
|
|
Scaffolder Backend Module Gerrit |
0.2.19 |
|
|
Scaffolder Backend Module Quay |
2.18.0 |
|
|
Scaffolder Backend Module ServiceNow |
2.15.0 |
|
|
Scaffolder Backend Module SonarQube |
2.15.0 |
|
|
Scaffolder Backend Module Utils |
4.1.2 |
|
|
Search Backend Module Azure DevOps |
0.5.0 |
|
|
Security Insights |
3.3.1 |
|
|
SonarQube Backend |
1.1.1 |
|
|
Tekton |
3.37.0 |
|
4.1. Troubleshooting
Plugin not loading
If a plugin fails to load, perform the following checks:
-
Verify the
ghcr.iopath is correct and the image tag or digest exists. -
Confirm your cluster has network access to
ghcr.io. - Review Developer Hub logs for OCI pull errors.
Determining tag values
The <tag> variable is your RHDH application's version of Backstage and the plugin version, in the format: bs_<backstage-version>__<plugin-version> (note the double underscore delimiter).
To find the correct image tag for
<tag>:- Look in the RHDH release notes preface for your Backstage version.
-
Locate the plugin version for paths starting with
oci://ghcr.iowithin one of the tables in the Dynamic Plugins Reference guide.
For example, because RHDH 1.9 is based on Backstage 1.45.3, the tag will have the format bs_1.45.3__<plugin-version>.
To ensure environment stability, use a SHA256 digest instead of a version tag. See Determining SHA256 Digests.
Determining SHA256 digests
You can look up the SHA256 digest using the Skopeo CLI or by searching in the RHDH Plugin Export Overlays repository.
Skopeo CLI
Ensure you have skopeo and jq installed.
- Locate the plugin path in the Dynamic plugins reference.
Run the following command, replacing the plugin path prefix
oci://withdocker://:skopeo inspect docker://<plugin-path>:<tag> | jq '.Digest'
RHDH Plugin Export Overlays Repo
Go to the plugin packages list in the rhdh-plugin-export-overlays repository. Search for your plugin and select the tag that is associated with this release.
4.2. Additional resources
5. Deprecated plugins
Red Hat Developer Hub (RHDH) includes several deprecated plugins, which are no longer being actively developed. Migrate to an alternative solution as soon as possible, because these plugins will be removed in a future release.
RHDH includes the following 0 deprecated plugins.
6. Other installable plugins
The following Technology Preview plugins are not preinstalled and must be installed from an external source.
These features are for Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information on Red Hat Technology Preview features, see Technology Preview Features Scope.
| Name | Plugin | Version | Installation Details |
|---|---|---|---|
|
Ansible Automation Platform Frontend |
1.0.0 | ||
|
Ansible Automation Platform |
1.0.0 | ||
|
Ansible Automation Platform Scaffolder Backend |
1.0.0 |