-
Notifications
You must be signed in to change notification settings - Fork 440
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
Use WebIdentityTokenCredentialsProvider to access remote extensions #4921
Conversation
1264 tests run: 1211 passed, 0 failed, 53 skipped (full report) |
looks awesome! |
Created a PR with my suggestions: #4922 |
We must next add e2e test that we are able to do these requests because of this new provider. Unsure how to setup such situation, or how to create a webidentity thing for the run. |
Review comments on #4921: - check the WebIdentity provider before imdsv2 because imds will do a http request which will cost more than checking local env variables - move provider config to be nearer to webidentity provider - refactor out the common wrapping of `aws_config::...::Region`
It will be covered by remote extensions e2e test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have anything to say about the code. If it works, it works 👍
Fixes access to s3 buckets that use IAM roles for service accounts access control method