Update Docker alias
to allow AWS SSO + additional clarity
#368
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.
What changed?
alias
in the documentationRationale
-e HOME
was required in order to make AWS SDK figure out where the.aws/sso/cache
folder lives-e AWS_PROFILE
was changed to pick up the current profile when runningiambic
as an alias<local_dir\>
was changed for clarity-v ${HOME}/.aws:/app/.aws:ro
was changed since write access to this directory should not be requiredHow was it tested?
If it was manually verified, list the instructions for your reviewers to follow.