End to End Testing AWS (Quick Start / Standard / Advanced )

[balasgit]

• [ ] Can we add the README about which describes about quickstart , standard and advance since its empty ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/aws
• [ ] As part of the README, I assume there will be link to describe the Gitops BOM which is getting along storage https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/aws/_common/gitops
• [ ] Can we add the Readme to describe the BOM Steps in the AWS Quick Start since no README exist ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/aws/openshift/1-quickstart
• [ ] Can we add the Readme to describe the BOM steps in the AWS Standard since no README exist ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/aws/openshift/2-standard
• [ ] Can we add the Readme to describe the BOM steps in the AWS Advanced since no README exist ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/aws/openshift/3-advance
• [ ] Make sure runtime Colima runtime is replaced with docker or multipass based on today announcement (https://gsicsi.slack.com/archives/C039DRPL77U/p1660840741635939)

[balasgit]

To be discussed:

BOM folder will be generated ONLY after we run the generate.sh so the BOM links will NOT work in the automation solutions folder.

Suggestions :

• Can we point to BOM YAML file instead of folder ?
• If we do, BOM YAML generated name is different than file exist in the files folder.

[balasgit]

As per discussion with sean, we are NOT expecting the README BOM links to be working inside the Files Folder.

• Purpose of this BOM links to be working in the published automation folder such as automation-integration-* , automation-turbonomic-***