End to End Testing - CP4D Data foundation

[balasgit]

Documentation discrepancies

• [ ] No Readme exist which is required to describe the list of BOM needed
• [ ] Can we remove the coming soon from the Folder Level Readme ?
• https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/software/cp4d/files
• [X] Can we remove the CP4D 3.5 link from the README https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/software/cp4d/files
• [X] Can we add the version for the CP4D 4.0 or 4.5 in the README since there is no version mentioned except the link to 3.5 ?
• [X] Can we links for BOM layer since its broken at https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/software/cp4d/files#data-foundation-layered-installation ?
• [ ] Can we add the links for optional components since its moved ?
• [ ] Make sure runtime Colima runtime is replaced with docker or multipass based on today announcement (https://gsicsi.slack.com/archives/C039DRPL77U/p1660840741635939)

[triceam]

When implementing automated testing, we should also regenerate from the latest BOM to include the latest modules and README docs.

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