-
Notifications
You must be signed in to change notification settings - Fork 70
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
🚀 Add S3 Implementation #227
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add the new storage in the workflow files in the root of the repository under .github
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add the new storage here https://github.com/gofiber/storage/blob/main/README.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add some tests in the s3_test.go file
What about just accepting an S3 connection for the config? |
My rationale for having our own config is that the storage implementation's interface / config should not depend on an S3 struct, so if S3 implementation were to change then fiber's S3 storage implementation can change without breaking the interface to initialise it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
@pcen any news about finishing this? |
The code functionally all works, @hi019 requested changes for some small code cleanup, otherwise all that's left is to somehow test with the GitHub CI, I haven't had time to look into how to do it, but if someone else figures it out before I have time to it's ready to merge |
I need s3 in one of my projects and this storage can ease my work. So i'll try to finish this PR. Btw i'm not sure about SDK version. What about using v2? @pcen |
When I started, I don't think v2 was available. Looking at the Amazon SDK repo for golang, it looks like the latest release is on v1.42.45. If you use the latest release version, it shouldn't cause any issues. If there is a newer version of the SDK, until it is implemented in golang, it won't effect us. |
Amazon has repo for go v2 sdk (https://github.com/aws/aws-sdk-go-v2) Btw we need to enter env variables(creditianals) for exexuting tests. I think we don't need to add tests because of that. Like https://github.com/gofiber/storage/blob/main/dynamodb/dynamodb_test.go @ReneWerner87 @hi019 What do you think? |
Had no idea about v2! in which case, we should definitely be using it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please check all workflows, think something needs to be adjusted there, add the new storage to the readme in the root, so this is obvious as storage variant
and the unittests are still insufficient, they need to be extended, so we can deliver the quality the users are expecting from us
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for finishing this 👍
Adds S3 implementation of the Storage interface