Conversation
756d2ac to
d806904
Compare
d806904 to
f18ec54
Compare
This was referenced Feb 19, 2023
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.
The
exec --jsonflag was always a bit weird, because the--jsonflag changes the behaviour and doesn't "exec" anything at all.This remedies that weirdness by creating a
aws-vault exportcommand that exports credentials in a variety of formats.aws-vault export --format=env PROFILEprints in env-var format e.g.FOO=BARaws-vault export --format=export-env PROFILEprints in env-var format with en export e.g.export FOO=BARaws-vault export --format=json PROFILEprints in json format compatible withcredentials_processaws-vault export --format=ini PROFILEprints in ini format compatible with~/.aws/credentialsThe old
exec --jsonflag still works but also prints out a deprecation notice to stderrFixes #761 #816