fix(store): resolve and refresh AWS role credentials - #60
Draft
tobi wants to merge 1 commit into
Draft
Conversation
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. Co-authored-by: Claude <noreply@anthropic.com>
This was referenced Sep 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use the AWS default credential provider chain when both configured static-key variables are absent. Resolve identity at startup and retain the provider for refresh. Explicit complete keys take precedence; partial or empty keys fail instead of falling through to another identity.
Adapts #48. Five isolated synthetic STS/S3 credential tests pass locally, including startup failure, explicit-key precedence and refresh. No live cloud identity is claimed.
Stack layer 2/8; base: backlog/01-conditional-storage. Review the diff against this base. Combined tree at 4475bb4 passes local
just ci(38 e2e tests, 19 serial simulations and standalone smoke) and the real two-instance S3 push/maintenance/clone/fsck rig. All six ignored stress/benchmark tests and all 184 full TLC checks pass locally (15 new checks across two models). The follow-up at 37bc4cc changes only two shell test assertions to Bash builtins; it passes with a minimal PATH. All eight stack heads are green in hosted CI (26 jobs). This layer’s successful run.Review order: 01-conditional-storage → 02-s3-credentials → 03-lfs-batches → 04-lfs-metrics → 05-auth-boundaries → 06-dev-setup → 07-azure → 08-azure-events.