Support an aws_credential_provider connection parameter for more flexible credentials strategies #1667
Conversation
This file contains 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
ruflin
approved these changes
Oct 17, 2019
jeskew
force-pushed
the
feature/support-credential-provider-in-awsauth-transport
branch
from
c5f8ea8 to
a83a3c6
Compare
…ible credentials strategies
jeskew
force-pushed
the
feature/support-credential-provider-in-awsauth-transport
branch
from
a83a3c6 to
6ebafe2
Compare
|
@ruflin Sorry for the radio silence on this PR! I added a changelog entry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Intended to address #1651. This PR updates the AWSAuthV4 transport to support an additional configuration parameter (
aws_credential_provider) to allow users to supply a callable credential provider. This would let users customize their provider to include caching, fetch credentials from a non-standard location, etc.