Migrate to v2 of the AWS Java SDK for S3 #27969
Draft
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.
This is partial, it only updates one usage of S3. Before this can be merged all usages should be updated, so opening as draft for now.
Paired with @rtyley
Changes so far
Panda
Panda settings require an instance of an
S3BucketLoader
. Panda comes with a default implementation for v1, but not v2, so this change creates one.This first requires a synchronous S3 client, which has been added to the
AWSv2
object alongside the existing asynchronous S3 client. Creating it here, rather than in the controller as before, allows it to be used more widely.Then the
getObject
method can be applied, with aResponseTransformer
to retrieve the "content" of the response, i.e. the object itself.