ibm-mas
Add IBM entitlement key validation
Feature and motivation
When an ibm-entitlement-key that includes extra characters is provided, the installation fails in the DRO/uds task. Error message can be one of the following inthe ibm-metrics-operator-controller-manager pod:
"error": "unable to decode jwt: could not base64 decode signature: illegal base64 data at input byte 43"
"error": "no redhat-marketplace-pull-secret or ibm-entitlement-key secret found, secret is required in a connected environment"
This may be avoided by putting a validation step for the ibm_entitlement_key value.
Usage example
This enhancement will save time for the installation and also reduce the customer tickets to support.
If mas install command is ran interactively, a feature in section 7 asking for the IBM entitlement key can be added checking if the value is ok. If not, the interactive install will stop.
