Skip to content
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

feat(sqs:large-message): Expose SDK v2 s3 client #602

Merged
merged 2 commits into from
Nov 5, 2021
Merged

Conversation

pankajagrawal16
Copy link
Contributor

@pankajagrawal16 pankajagrawal16 commented Nov 1, 2021

**Issue #597

Description of changes:

Checklist

Breaking change checklist

RFC issue #:

  • Migration process documented
  • Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@pankajagrawal16 pankajagrawal16 changed the title feat: Expose SDK v2 s3 client feat(sqs:large-message): Expose SDK v2 s3 client Nov 1, 2021
@@ -180,4 +180,31 @@ processing.
return "ok";
}
}
```

## Passing custom S3Client
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider a change to Overriding the default S3Client to match the method name.


## Passing custom S3Client

If you need to pass custom S3Client such as region to the SDK, you can pass your own `S3Client` to be used by utility either for
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wording change.

"If you require customisations to the default S3Client, you can create your own S3Client and pass it to ......"

Copy link
Contributor

@msailes msailes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants