-
Notifications
You must be signed in to change notification settings - Fork 7
Implement AWS SDK v2 #24
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
Conversation
|
Related to #14 |
|
Related: #21 |
|
Also, checking the docs and for solving #18 we could take a look at: https://pkg.go.dev/github.com/aws/[email protected]/aws#CredentialsCacheOptions |
|
Related to #9 |
|
Ready for a rebase. |
|
thanks for this PR. I can help by testing it after you address my comment about reusing the buffer. |
|
Changes implemented, however with the new golangci linting I get an error on This would break the current plug&play implementations, maybe we should raise exception in the CI for this? |
|
You can add a |
|
Will test the latest revision today and post results here. |
|
While testing the latest version, I'm getting this error in the prometheus logs. I'm trying to troubleshoot the issue. |
|
I tested the latest version with the latest version of Prometheus and it works! thanks! |
|
Implemented all the suggested changes, however I've one little concern related to AssumeRole, @rapphil could you test that? I'll ping the review to the exact line |
|
Ok, I tested with/without assume role and it works in both case. I can see the assumed roles credentials being fetched every 15 minutes (a little bit before that actually because of the cache). |
|
This needs a quick rebase to pick up go.mod changes. |
|
Also, if you would please squash the commits into logical changes so the commit log is not so messy. |
|
@SuperQ I think I cleaned a little the commit history, if you need more changes or even smaller commit history let me know! |
|
@SuperQ can comment before you take any action, but IMHO this PR is small enough to be a single commit. So if SuperQ agrees, maybe you can squash everything into a single commit. |
|
I can squash everything to one commit if you feel like it, however, I don't see the difference between doing that in my git branch and setting that on the PR config, as this repo doesn't have high PR/Commit rate |
|
I can squash and merge, but then I have to manually cleanup the commit message. Please squash your commit history so this is only one commit. In the future, I recommend you use "fork and branch" PR workflows so you do not have changes to |
|
Done @SuperQ , thank you for your advice about fork and branch, I'll for next PRs :) |
Signed-off-by: Miguel Angel Sanchez <[email protected]>
Signed-off-by: Miguel Angel Sanchez <[email protected]>
Signed-off-by: Miguel Angel Sanchez <[email protected]>
|
Will reopen new PR correctly, I wasn't able to recover git history |

Migrated all the AWS SDK v1 to v2.
May need some checks with a product implementation to confirm it works correctly.