-
Notifications
You must be signed in to change notification settings - Fork 890
Added comments in migration tool for unsupported method #6018
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
base: master
Are you sure you want to change the base?
Conversation
@@ -199,12 +199,12 @@ public void requestconstructor() { | |||
.build()); | |||
|
|||
//INCOMPATIBLE RESPONSE |
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.
If the newly added comment is single line can we use//
Single-line comment for the new comment added
@@ -199,12 +199,12 @@ public void requestconstructor() { | |||
.build()); | |||
|
|||
//INCOMPATIBLE RESPONSE | |||
s3.getBucketAccelerateConfiguration(GetBucketAccelerateConfigurationRequest.builder().bucket(bucketName) |
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.
why does V1 style from /before/
s3.getBucketAccelerateConfiguration(new GetBucketAccelerateConfigurationRequest(bucketName));
gets converted to V2 when it says Transform is not supported ?
…aws-sdk-java-v2 into bole/s3Clients_not_supported_method
|
Motivation and Context
Some S3 method will not be supported in migration tool and will require manually migration. This change added comments before those method to address that. Once the dec guide is updated on how to manually migrate those method, the link to the dev guide will be added in future PR.
Modifications
Added method name check in S3NonStreamingRequestToV2.java recipe
Testing
Changed the test cases in integration test
Screenshots (if appropriate)
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License