EPIC Goal

What are we trying to solve here?
The docs repo has a script that is used to generate various tables of (Supported, Community, TP) plugins. These tables are essential for customers since they are the source of truth for compatible plugin versions and paths to OCI artifacts needed in the wiring of their configs. We need to ensure the script/automation are robust and reliable

Background/Feature Origin

During 1.9 shutdown, numerous issues were discovered (missing plugins, incorrect SHA256 digests/plugin paths, inconsistent lifecycle states, etc) which led to unnecessary churn and confusion

Why is this important?

Our docs need to be trusted. Our process that generates these docs need to be reliable

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>