Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CS4108195 - Output format of "/usr/local/bin/ibmcloud resource service-key xxxxxx" was changed recently. #411

Open
gaskinner84 opened this issue Sep 23, 2024 · 0 comments

Comments

@gaskinner84
Copy link

Customer created a support ticket on 2024-09-19 21:51:36:

Output format of "/usr/local/bin/ibmcloud resource service-key xxxxxx" was changed recently.
This is very big impact against our product.

$ /usr/local/bin/ibmcloud resource service-key XXXXXXXX
cos_hmac_keys:
(space) access_key_id: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
(space) secret_access_key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

The number of spaces was increased.   Please restore it.

Our script can not get credential . I am not asking to check our script.
This script is installed into over customer's 200 devices.

This changed in the last few days clearly.
Tried to create new bucket and credentials . same result.
The problem is "output format was changed" The existing credentials are not lost.

ACS escalated this to COS and here was their response:

I don’t see any issues with the COS CLI plugin. It seems like a CORE CLI issue where extra spaces are being added.
The COS CLI plugin always starts with 'ibmcloud cos'.
Could you please re-assign the ticket?
Escalate the problem to the CORE team via internal ticketing (GHE) ? Also, it appears that this issue could have stemmed under a specific scenario where customer could be extracting (cut ) certain number of characters. It may be feasible asking the customer on how they fetching the details of the access key and suggest a workaround (like awk 3rd column or so).

Regards,

Gary S.
Lead, Storage Support Engineer
IBM Cloud Support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant