Epic Goal

Create a process by which external components and contribute their image and SHA to the bundles, for releases and dev builds.

This is to replace the Automation and tags currently used in CPAS?

Why is this important?

Using tags requires the external component team to remember to use a SHA at release, to guarantee the providence for the shipped image. Moving strictly to SHA"s guarantees the trail of providence fort he images in dev and release.

Scenarios

Dev build versions of images like volSync, Gatekeeper, etc...

Acceptance Criteria

Documented, repeatable procedure that enables the MCE/ACM bundles.

Dependencies (internal and external)

External components, there are 7:

List kbempah 

1. VolSync
2. Gatekeeper
3. Hive
4. Assisted
5. Obs
6. GlobalHub??
7. Edge Management?
8. SiteConfig
9. IBIO??

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>
• Considerations were made for Extended Update Support (EUS)