Adding Environment Variable Credential Support #13
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 pull request resolves issue #12 by allowing the user to utilize AWS credentials in environment variables. this is done by injecting the following environment variables into the container when executing commands:
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_SESSION_TOKEN
AWS_SECURITY_TOKEN
This will allow users to utilize tools such as https://github.com/segmentio/aws-okta to run the application. In order to use this functionality instead of using a profile, I have added the
--env
flag to load credentials via environment variable instead of aws profile. When the--env
flag is used and a database is not specified, I have it default togeneral.db
for lack of a better name.I have tested this on several of our accounts with success. If you have any suggested changes please let me know!