The COS role uses IBMCOS_RESOURCEGROUP to allow COS specific setting of the group, but does not do the same for the API Key, this means that we are forced to use an over-priviledged API key for the COS integration ... it should work the same way:
ibmcos_apikey
ibmcos_resourcegroup
The MAS tekton piptlines and CLI will need matching updates too.
The COS role uses
IBMCOS_RESOURCEGROUPto allow COS specific setting of the group, but does not do the same for the API Key, this means that we are forced to use an over-priviledged API key for the COS integration ... it should work the same way:The MAS tekton piptlines and CLI will need matching updates too.