User Story

As an OpenShift engineer I want the CAPI Providers repositories to use the new generator tool so that they can independently generate CAPI Provider transport ConfigMaps

Background

Once the new CAPI manifests generator tool is ready, we want to make use of that directly from the CAPI Providers repositories so we can avoid storing the generated configuration centrally and independently apply that based on the running platform.

Steps

• Install new CAPI manifest generator as a go `tool` to all the CAPI provider repositories
• Setup a make target under the `/openshift/Makefile` to invoke the generator. Make it output the manifests under `/openshift/manifests`
• Make sure `/openshift/manifests` is mapped to `/manifests` in the openshift/Dockerfile, so that the files are later picked up by CVO
• Make sure the manifest generation works by triggering a manual generation
• Check in the newly generated transport ConfigMap + Credential Requests (to let them be applied by CVO)

Stakeholders

• <Who is interested in this/where did they request this>

Definition of Done

• CAPI manifest generator tool is installed 

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>