-
Notifications
You must be signed in to change notification settings - Fork 546
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
Feature Request: Update S3 module with AWS CLI 2.0 SSO integration #2150
Comments
To set expectation: as we, Mozilla, don't need it currently, aren't going to work on it. So, contributions are welcome |
Alright, I can look into it. Thanks. Do you folks not use the S3 back end internally, or are you folks just still using AWS CLI V1? If it's the latter I encourage looking into upgrading. |
We moved to gcp :) |
Does anyone know if this should be part of opendal? |
@Saruniks From what I recall when digging into this, the behavior is due to sccache integrating with opendal when opendal only supported environment variables for AWS auth. Today, opendal can automatically load credentials for valid AWS CLI sessions without the use of environment variables. It's been a while since I investigated this, so the details are a bit fuzzy but hopefully correct. |
Hi Folks,
This issue in an unrelated project explains the same issue. Currently sccache doesn't pick up credentials when logged into AWS CLI v2 with SSO.
Is it possible to add support for this?
The text was updated successfully, but these errors were encountered: