Rename CatalogSource to ibm-maximo-operator-catalog

[sva-andreasb]

Feature and motivation

We are using RHACM to manage our OpenShift Cluster which has various IBM products installed. They use the ibm-operator-catalog found at icr.io/cpopen/ibm-operator-catalog:latest in a CatalogSource named ibm-operator-catalog.

With the CatalogSource enforced by RHACM, the correct image for the ibm-operator-catalog for Maximo gets overwritten and we are unable to install. Renaming CatalogSource ibm-catalog-operator to ibm-maximo-catalog-operator would

• circumvent this problem
• be more correspondend between CatalogSource name and image name

I renamed it for a test with grep -rli 'ibm-operator-catalog' /home/user/.ansible/collections/ansible_collections/ibm/mas_devops/ | xargs -i@ sed -i 's/ibm-operator-catalog/ibm-maximo-operator-catalog/g' @ and this seems to work fine

Usage example

Same usage as before, just easier to manage

[durera]

The issue lies with the fact that the MAS product itself has some code inside it whereby it assumes the catalog source is named "ibm-operator-catalog" ... we can very easily change the ansible collection to support any named catalog (it's been on the todo list for a while), but we must also introduce changes to the product that will allow the management of MAS installed from a source named something other than ibm-operator-catalog, otherwise if you use a different name then you wouldn't be able to - for instance - add or remove or modify applications from the MAS admin dashboard.

This is definitely on the to-do list, but it's not as straightforward as it may at first seem, due to the need to change product code across all supported releases as well.