COS role should use a targeted variable for IBM Cloud API Key #1346
Labels
Critical - Tracked in Jira
Issues that have been escalated internally and are tracked in Jira now
Improvement/Tweak
Small improvement or tweak to existing capability
Quick Fix
Milestone
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:The MAS tekton piptlines and CLI will need matching updates too.
The text was updated successfully, but these errors were encountered: