-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
AWS SSO CLI v2 does not work #119
Comments
Hi @brainstorm This feels like the best workaround I've found until this is fixed: |
Indeed, I'm using this one instead: |
Hi @lucagrulla, it looks like the AWS Go SDK now supports AWS SSO: https://aws.amazon.com/blogs/developer/aws-sso-support-in-the-aws-sdk-for-go/ I'm a huge fan of I am used to the workaround mentioned above with aws-sso-util -> yawsso, but it would be helpful for other members of my team if I didn't have to write out instructions on how to use the workaround :) Would you consider re-opening this issue, in case anyone wants to take this on? |
Thanks @kmcquade. The issue is nor re-opened. |
Released with v4.1.3 |
Describe the bug
The new AWS CLI v2 provides Single Sign On:
https://aws.amazon.com/blogs/developer/aws-cli-v2-is-now-generally-available/
But doesn't seem to play well with
cw
:$ cw ls -p dev groups no valid providers in chain. Deprecated. For verbose messaging see aws.Config.CredentialsChainVerboseErrors
To Reproduce
The text was updated successfully, but these errors were encountered: