-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Separate S3Control methods from S3 #4745
Separate S3Control methods from S3 #4745
Conversation
@mikegrima I believe you implemented this feature originally - any objections to this change from your side? |
Hi @bblommers! As long as all of the previous functionality will work properly then I'm OK with the change. Is the breaking change that instead of |
Correct @mikegrima - it's just a matter of using the new decorator from 3.x. None of the logic has changed. |
LGTM |
Thanks @mikegrima! |
Codecov Report
@@ Coverage Diff @@
## master #4745 +/- ##
=======================================
Coverage 95.01% 95.02%
=======================================
Files 575 580 +5
Lines 61324 61343 +19
=======================================
+ Hits 58268 58289 +21
+ Misses 3056 3054 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
This is now part of moto >= 3.0.0.dev5 |
The S3-module contained three methods that were technically part of
S3Control
:Because they were part of the S3-module, it needed the S3-mock:
This PR extracts the logic into a dedicated module, making it more discoverable and obvious that we support these methods.
This means users now have to use the dedicated
mock_s3control
:This is a breaking change, so it will only be merged as part of the next major release.
Note that none of the existing logic or tests have been changed as part of this PR - only moved around.