Repository navigation
fix(store): resolve and refresh AWS role credentials - #61
Conversation
yordis
commented
Oct 31, 2026
- The S3 store refused to start without static access keys, so hosts running under an IAM role, IRSA or another AWS identity could not use S3 at all, while S3 is meant to be as first class as GCS.
- Role credentials expire; the store has to refresh them through the provider instead of signing with a snapshot taken at startup.
- A partial or empty explicit key pair must fail closed instead of quietly falling back to some other identity.
- Brings in fix(store): resolve and refresh AWS role credentials tobi/walgit#60 by Tobi Lütke, cherry-picked with original authorship; adapted so the mutation and read clients share one credential cache and exchange role credentials once.
PR SummaryMedium Risk Overview Explicit keys still win, but partial config fails closed. Non-empty Docs ( Reviewed by Cursor Bugbot for commit 0f43a99. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 47 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
f7344b7 to
0cdf9bd
Compare
Adapt PR #48 onto conditional storage fixes. Keep explicit credentials fail-closed; retain the provider for automatic refresh. Synthetic STS/S3 credential tests: 5 passed. The mutation and read clients share one resolver and identity cache so role credentials are exchanged and refreshed once, not once per client. (cherry picked from commit 0372cb9) Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
0cdf9bd to
0f43a99
Compare