Remove S3 code that was obsolete in V3 for V4. #3686
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Deleted all obsolete code in S3 package for V4. Initially I thought I would leave some in but given that we want to look at auto generating S3 at some point I figured it would be best to remove as much customization logic as possible.
The obsolete code I was most on the fence about deleting
Expires
property in favor ofExpiresString
.GetAcl
andPutAcl
service methods. We have created new gets and puts per object and bucket which map to the S3 model. I debated about keeping this obsolete code to give an easier migration but since this was the SDK moving closer to the model it seemed better for a future auto generation effort.Testing
Dry Run: DRY_RUN-bd4e3e24-9cd1-4569-a2b7-eb07c6ae51eb Successful