-
Notifications
You must be signed in to change notification settings - Fork 8
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
Looging in with API key fails #19
Comments
Manually logging in by adding the below step, works: - name: Login to IBM Cloud
run: |
ibmcloud login --apikey ${{ secrets.IBMCLOUD_API_KEY }} -r ${{ env.IBM_CLOUD_REGION }}
ibmcloud cr login |
I see the name you are using to reference the API key is different in each example. + secrets.IBMCLOUD_API_KEY
- secrets.IBM_CLOUD_API_KEY |
Sorry. That's just a typo. It still fails with the correct secret.
|
@digorgonzola Can you try the following as a manual login? Asking because of 2 reasons. 1. we don't use the --apikey parameter, but instead use the ENV var and 2. we pass the group parameter. This should be closer to what we do under the covers in the action. - name: Login to IBM Cloud
env:
IBMCLOUD_API_KEY: ${{ secrets.IBMCLOUD_API_KEY }}
run: |
ibmcloud login -r ${{ env.IBM_CLOUD_REGION }} -g default
ibmcloud cr login |
Yes the following works fine:
Unsure then why it fails with the action... |
For a full comparison, can you please also include the group in your command?
|
Using this action with an API key fails with exit code 1:
Workflow:
The text was updated successfully, but these errors were encountered: