Summary

Once we have an ET release and product-config, we need to migrate/onboard all current MCGH components in the acm-cpaas-midstream into that product-config, specifically by populating the builds array.  Once populated, we need to verify the components list, update them, and ensure the components build, debugging failures. 

To do:

Product definition:

• Add all MCGH builds to the product.yml and release.yml
• Verify the list

Midstream repository:

• Create new midstream repository branch with content from ACM 2.7 temporary onboard
• Fork the midstream project
• Update upstream sources and Dockerfile.in in the fork

CPaaS scratch build:

• Run CPaaS pipeline-seed to read the product definition and generate the Jenkins build environment
• Create a midstream merge-request with the above edits, which generates a Jenkins check-patch job
• Debug build failures until non-bundle builds succeed
• Merge the changes to dist-git once the check-patch passes.