Streamline credentials configuration #35
Open
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.
Note: Depends on #32
Currently, it's required that the user manually set the credentials after the container's creation by using
SEToraws_commons.create_aws_credentials.This pull request makes it much easier to jump into using the tool. Instead of having to set the aws credentials from userspace, they are now set by docker compose. Those functions can now be used to override the default credentials.
Docker compose changes:
environmentproperty as opposed toenv-fileinstead of splitting between bothUpdated docs:
plpython3uusage with docker-compose instead ofplpythonuCleanup: