Skip to content

Support explicitly specifying the boto3utils3.s3 object#92

Merged
philvarner merged 3 commits into
stac-utils:mainfrom
philvarner:pv/explicit-s3
Mar 8, 2024
Merged

Support explicitly specifying the boto3utils3.s3 object#92
philvarner merged 3 commits into
stac-utils:mainfrom
philvarner:pv/explicit-s3

Conversation

@philvarner
Copy link
Copy Markdown

Task.upload_item_assets_to_s3 and asset_io.upload_item_assets_to_s3 support explicitly specifying the boto3utils3.s3 object

This allows greater flexibility in setting various AWS S3 parameters, which allows this to support S3-compatible APIs like MinIO.

@philvarner philvarner merged commit 579ba7b into stac-utils:main Mar 8, 2024
@philvarner philvarner deleted the pv/explicit-s3 branch March 8, 2024 14:12
Copy link
Copy Markdown
Member

@ircwaves ircwaves left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent added flexibility. 👍🏽

Question/suggestion: what about moving the s3_client parameter from the signature of Task.upload_item_assets_to_s3 to the constructor, and have the if None defaulting to self._s3_client = s3() happen there? Then upload_item_assets_to_s3 could use self._s3_client, and potentially/eventually download_item_assets could too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants