Cert management by Hive was not implemented originally (deemed a future item), leaving downstream teams facing the challenge of building code to deal with it independently of each other - goal is to handle cert management through the API so that downstream teams can deprecate their individual implementations and utilize the Hive implementation
Why is this important?
…
Scenarios
...
Acceptance Criteria
CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
...
Dependencies (internal and external)
...
Previous Work (Optional):
…
Open questions::
…
Done Checklist
CI - CI is running, tests are automated and merged.
Release Enablement <link to Feature Enablement Presentation>
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 Polarion: <link or reference to Polarion>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>
Epic
Minor
