Value Statement

Using the OCP/CAPA repo  as our source to build MCE/CAPA images is hard to maintain and support bug fixes  due to different version release cycle and the ownership of the repo. We need to fork the upstream/CAPA repo under stolostrone organization at github in order to have the owner ship of the repo and easily maintain update our ROSA HCP work.

Definition of Done for Engineering Story Owner (Checklist)

• Have the CAPA upstream repo fork in stolostrone github organization 
• Create Docker file the build the CAPA upstream source code using redhat base images
• Collaborate with ACM release team to build and publish the new CAPA image
• Discontinue mirroring the image build from OCP/CAPA to acm-q 

Development Complete

• Having a DockerFile to build the CAPA source-code using non entitlement
  • entitlement image is like ocp/4.19:base-rhel9 we need to use ubi9/ubi-minimal

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.