Add boto3 in Dockerfile to support s3-like artifact access #4
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
cgoudet-foodles
approved these changes
Jun 10, 2022
cgoudet-foodles
left a comment
cgoudet-foodles
left a comment
There was a problem hiding this comment.
Thank you for these changes I am expecting too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Attempting to view artifacts stored on an s3-like object store results in an error "Loading Artifacts Failed..." because the
boto3package is not installed.This PR adds
boto3to thepipcommand in theDockerfileto add support for the server to access artifacts in s3-like object stores.