-
Epic
-
Resolution: Unresolved
-
Blocker
-
None
-
None
-
Correct status of community plugins (azure, servicenow, http-request scaffolder plugins)
-
False
-
-
False
-
-
In Progress
-
RHDHPLAN-906 - [Doc] Announce downgrade to Community support for 5 plugins in a future release
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
57% To Do, 14% In Progress, 29% Done
-
-
-
Important
EPIC Goal
What are we trying to solve here?
1.9 docs incorrectly lists the following as community plugins falling under the scope of TP support:
@backstage/plugin-scaffolder-backend-module-azure @roadiehq/scaffolder-backend-module-http-request @backstage-community/plugin-scaffolder-backend-module-servicenow
Background/Feature Origin
As discussed in group DM with PM and docs, only azure and service now are community supported while http-request is GA supported
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>
