Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate the possibility of implementing AWS S3 API #185

Closed
ikopylov opened this issue Mar 4, 2021 · 0 comments · Fixed by #193
Closed

Investigate the possibility of implementing AWS S3 API #185

ikopylov opened this issue Mar 4, 2021 · 0 comments · Fixed by #193
Assignees

Comments

@ikopylov
Copy link
Member

ikopylov commented Mar 4, 2021

https://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html

@ikopylov ikopylov changed the title Investigate the possibility of implementing the AWS S3 API Investigate the possibility of implementing AWS S3 API Mar 4, 2021
@vovac12 vovac12 self-assigned this Mar 28, 2021
vovac12 added a commit that referenced this issue Apr 7, 2021
piakushin pushed a commit that referenced this issue Jul 27, 2021
* Add api method for get data

* Add API method for put data

* Add converters from Error to StatusExt

* S3: GetObject implementation

* Use default bucket name

* GetObject and PutObject fully implemented

* Fix naming and use pattern matching for error handling

* Handle request headers for GetObject

* Fix DateTime parse and remove unneeded header handlers

* Use kind() method instead of public attribute

* gh-185 Add CopyObject method

* unwrap_or_else instead of match

* Replace match by if-let statements

* import IoError and BobError

* Remove unnecessary error conversion

* Update CHANGELOG.md
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 a pull request may close this issue.

2 participants