feat: add --profile-env flag to exec command#340
Open
tthayer wants to merge 1 commit intoByteNess:mainfrom
Open
feat: add --profile-env flag to exec command#340tthayer wants to merge 1 commit intoByteNess:mainfrom
tthayer wants to merge 1 commit intoByteNess:mainfrom
Conversation
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.
This change adds a
--profile-envflag to theexeccommand in order to allow profile-based SDK calls to authenticate. Setting--profile-envwill cause a token file to be created (default is~/.aws/sso/cache) with a filename that matches the sha1 of the start URL. My startURL value has a hash symbol in it so the IgnoreInlineComment option needs to be passed so it won't strip it out of the string value. This is needed in order to generate the correct SHA1. When--profile-envis set, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY are not set in the environment and instead AWS_PROFILE is set to a value that matches the profile that was passed in at the CLI. If the tokenfile is being used for auth, it is checked for expiration and it is refreshed if needed.