End to End Testing - IBM Cloud (Quick / Standard / Advanced)

[balasgit]

Documentation Discrepancies:

• [ ] Can we fix the link in the README since BOMs references are broken at this moment ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/ibmcloud/openshift
• [ ] Can we add additional instructions for each BOM layer so it helps users to run the CLI ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/ibmcloud/openshift/1-quickstart/files#run-all-the-terraform-layers-manually
• [ ] Can we add image/fix the link which is not rendering https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/ibmcloud/openshift/2-standard/files
• [X] Can we fix all BOM Links which is not loading for both sections VPC with VSIs & VPC with Red Hat OpenShift ?
• [ ] Can we add image/fix the link which is not rendering https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/infrastructure/ibmcloud/openshift/3-advanced/files
• [X] Can we fix all BOM Links which is not loading for both sections VPC with VSIs & VPC with Red Hat OpenShift ?
• [ ] Make sure runtime Colima runtime is replaced with docker or multipass based on today announcement (https://gsicsi.slack.com/archives/C039DRPL77U/p1660840741635939)

[triceam]

We need to regenerate BOMS, but automated testing is already in place for this.

[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-***