At the moment, ods-ci image (MPS version) relies on OCM cli to create the Idenity providers. It adds the requirement of gaining and inserting OCM token while running the container. It may create issue in integrating with pipelines (CVP, MPS, etc). In general, pipeline would need to get somehow a token and store it for example in CI Vault or other like this. After that they would need t inject the token in cluster secrets.

We want to find a way not to use OCM to enlight the amount of actions and requirements of the containers. OC CLI should be sufficient to create the IDPs

UPDATE

Removing completely OCM wouldn't be possible because the IDP install script wouldn't be able to create IDPs in the following cases:

• run ODS-CI image from local
• run the install script from local without being logged in the cluster with a cluster-admin user (e.g., kubeadmin or Google IDP or a service account)

Hence, this story should implement the option for the user to select if they want to use OCM or OC to install IDPs. This would remove the need of an OCM token when running ODS-CI image as pod in a openshift cluster (e.g., as part of CVP testing)