End to End Testing - Maximo

[balasgit]

Documentation Discrepancies

• [X] Can we add version of Maximo will be installed along with its dependencies version too which helps users ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/software/maximo

• [ ] Can we remove coming soon from the README ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/software/maximo/files

• [ ] Can we fix the BOM Links which are broken ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/software/maximo/files#maximo-core-for-multi-cloud

• [ ] Can we add the ODF class which needs to be passed in the terraform files since we specified support for IBM Cloud ? https://github.com/cloud-native-toolkit/automation-solutions/tree/main/boms/software/maximo/files#-advanced-configuration-options

• [ ] Can we remove the multi-cloud if its not supported & tested since some places which says coming soon but other places supported ?

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