EPIC Goal

What are we trying to solve here?

Background/Feature Origin

There are a number of RHTAP owned plugins bundled with RHDH that do not have proper documentation. These are production level supported (reference: RHTAP RHDH Packaged Plugins)

• backstage-community-plugin-tekton
• roadiehq-backstage-plugin-argo-cd
• roadiehq-backstage-plugin-argo-cd-backend
• backstage-community-plugin-quay
• backstage-community-plugin-scaffolder-backend-module-quay

In our current docs, we have instructions for setting up Tekton and Argo CD but we do not have anything for Quay but it looks like it's in the docs repo . I don't believe we have documentation for scaffolder actions either.

Our permission policy reference is also missing permissions for Argocd and Quay which the upstream docs has.

Maybe this can be discussed with the RHTAP team, but they introduced a new backend plugin for Quay and RHDH has made the decision to not bundle any more plugins. If the backend plugin is intended for use in RHDH, we should document the location of this plugin or add a reference to the RHTAP doc.

Why is this important?

User Scenarios

Dependencies (internal and external)

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>