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

Upgrade to use awssdk v2 #47

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

skiyooka
Copy link

Addtionally upgraded sl4fj, java, and simplified test execution against S3.

Thank you @alexmojaki for your library. It provided a great solution and starting point to solve the creation of a large .zip from S3 files and stream the resulting .zip (of unknown size) back.

The ability to test directly against S3 is vitally important to ensure that the changes are working correctly and to assure that this library is safe to use. This testing uncovered an interesting detail that the eTag in awssdk v2 are surrounded by double quotes.

I took a look at jclouds, s3proxy, etc. and while they look interesting I did not have enough time to figure them out and I was also concerned by the lack of activity in jclouds. Hence I figured that for future users, the easiest approach would be to remove them altogether and allow those interested in running the tests to do so directly against S3.

Also thank you @alexwhiteoval for your PR. I reviewed it to ensure I didn't miss anything and you had a more elegant way to incorporate the customise* handlers.

Addtionally upgraded sl4fj, java, and simplified test execution against S3.

The ability to test directly against S3 is vitally important.
<groupId>software.amazon.awssdk</groupId>
<artifactId>sso</artifactId>
</dependency>
<dependency>
Copy link
Author

Choose a reason for hiding this comment

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

I provide my AWS credentials on the command line using aws sso login

@alexmojaki
Copy link
Owner

@skiyooka I no longer have time to maintain this library and I barely remember anything about Java or AWS. At this stage I think it would be best to archive this repository, link to your fork, and you can create a new package on maven or whatever repository people use nowadays. WDYT?

@skiyooka
Copy link
Author

@alexmojaki I'm flattered for the offer. I unfortunately don't have the bandwidth to become the maintainer either.

@skiyooka
Copy link
Author

I wanted to take the time to create this PR as I recognize good work when I see it... and this saved me a bunch of time to solve a difficult problem.

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.

None yet

2 participants