Add support for consuming credential_process in 'aws-vault exec'. #1087
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.
The AWS CLI supports calling an external credential provider via the
credential_process
configuration option. However, as stated in the AWS CLI Docs:I have a use case where I must call an external process to obtain a credential. I wish to cache this credential to avoid repeated API calls and 2FA prompts. Rather than rolling my own caching, I would prefer to make use of
aws-vault
for this purpose.This PR implements the equivalent
credential_process
logic inaws-vault exec
. I am aware of the existing use case of usingcredential_process
from the AWS CLI to invokeaws-vault
; I have attempted to differentiate these use cases in my edits to USAGE.md.