This document outlines the steps required to certify your plugin with Red Hat Developer Hub. Follow these instructions to ensure a smooth and successful certification process.
-
Fork the Certification Repository to your GitHub account.
-
Prepare a Certification Pull Request
Create a directory under
partner
with the name of your organization.Inside this directory, create a subdirectory with the name of your dynamic plugin.
Within this plugin directory, create another subdirectory using the version of the plugin as the directory name.
Finally, in this version directory, create a file called
package.yaml
.In the
package.yaml
file, add the content for your dynamic plugin. Below is an example structure and content:Directory Structure:
partner/ └── your-organization └── your-plugin └── v1.0.0 └── package.yaml
Example
package.yaml
Content:global: dynamic: plugins: - package: oci://quay.io/tkral/backstage-community-plugin-todo:v0.1.1!backstage-community-plugin-todo disabled: false
-
Submit the PR:
- Push your changes to your fork and create a pull request against the certification repository.
-
Automated CI/CD Pipeline:
- Your plugin will automatically be run through the certification pipeline:
- Compatibility checks with Red Hat Developer Hub.
- Smoke tests for basic functionality.
- Your plugin will automatically be run through the certification pipeline:
-
Review Feedback:
- Address any issues flagged during the automated pipeline.
- Incorporate feedback from reviewers.
-
Metadata Storage:
- Ensure the plugin’s metadata is stored in the designated repository for certified plugins.
-
Ongoing Maintenance:
- Monitor for updates to Red Hat’s certification requirements.
- Regularly update your plugin to ensure compatibility with new platform versions.
- Plugin Development Guidelines
- Certification FAQ
- Red Hat Support Portal