https://github.com/redhat-developer/rhdh-plugin-certification

rhdh-plugin-certification
https://github.com/redhat-developer/rhdh-plugin-certification

Last synced: 10 months ago
JSON representation

rhdh-plugin-certification

• Host: GitHub
• URL: https://github.com/redhat-developer/rhdh-plugin-certification
• Owner: redhat-developer
• License: apache-2.0
• Created: 2025-01-29T21:06:37.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2025-06-23T20:53:55.000Z (10 months ago)
• Last Synced: 2025-06-23T21:41:36.122Z (10 months ago)
• Language: Shell
• Size: 30 MB
• Stars: 2
• Watchers: 10
• Forks: 1
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
## Workflow for Certifying Your Plugin with Red Hat Developer Hub

#### 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.

### 1. Submit Your Plugin for Certification

1. Fork the Certification Repository to your GitHub account.

    

2. 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:**

   ```plaintext

   partner/

   └── your-organization

       └── your-plugin

           └── v1.0.0

               └── package.yaml

   ```

    

   **Example `package.yaml` Content:**

   ```yaml

   global:

     dynamic:

       plugins:

         - package: oci://quay.io/tkral/backstage-community-plugin-todo:v0.1.1!backstage-community-plugin-todo

           disabled: false

   ```

3. Submit the PR:

    * Push your changes to your fork and create a pull request against the certification repository.

### 2. Certification Pipeline

1. 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.

2. Review Feedback:

    * Address any issues flagged during the automated pipeline.

    * Incorporate feedback from reviewers.

### 3. Post-Certification

1. Metadata Storage:

    * Ensure the plugin’s metadata is stored in the designated repository for certified plugins.

1. Ongoing Maintenance:

    *  Monitor for updates to Red Hat’s certification requirements.

    * Regularly update your plugin to ensure compatibility with new platform versions.

### Additional Resources

* Plugin Development Guidelines

* Certification FAQ

* Red Hat Support Portal

#### For questions or assistance, contact the Red Hat Developer Hub support team at support@redhat.com.