Improve support for temporary IAM credentials in chat_bedrock() #266
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.
Many AWS IAM credentials expire, but previously we ignored this by looking up credentials only once, in
chat_bedrock()
. This commit introduces a caching layer that handles expiry and moves credential retrieval closer to request time, instead.The design is almost identical to httr2's OAuth token caching mechanism, but I had to re-implement various pieces because not all of that API is exported.
(We could probably introduce a
req_aws_credentials()
function tohttr2
itself that would handle this, but that might tie us too closely to the semantics ofpaws.common
.)Unit tests are included.
Closes #261.