-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
remove s3 legacy provider #11746
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
remove s3 legacy provider #11746
Conversation
Currently, only minor and patch changes are allowed on master. Your PR labels (aws:s3, semver: major) indicate that it cannot be merged into the master at this time. |
93c661a
to
6b60f35
Compare
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 3m 31s ⏱️ Results for commit 6662509. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ±0 2 suites ±0 1h 42m 22s ⏱️ - 2m 52s Results for commit 6662509. ± Comparison against base commit fb7cde9. This pull request removes 2 tests.
♻️ This comment has been updated with latest results. |
f222411
to
8bdcfb9
Compare
8bdcfb9
to
6662509
Compare
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.
Nice and clean deletion of the old S3 provider. 🧹 💯
Motivation
S3 v3 (fully native in LocalStack) has been the default since v3, and we deprecated and did not maintain the legacy v2 implementation and did not provide new features to it since then.
For the v4 release, we are removing the implementation and the associated tests.
Changes