Replies: 2 comments 1 reply
-
|
Also: aws/aws-sdk-go#5270, end-of-support will occur next year. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
cc @atoulme , @pdelewski |
Beta Was this translation helpful? Give feedback.
-
|
Closing as already reported in #33208 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
At the moment there are 3 exporters that leverage the AWS Go SDKs:
Only Kinesis uses v2, the other two use v1. I was wondering if it could be relevant to standardise to using v2. One of the advantages would be to be able to get request IDs (as well as some other metadata) from S3, which can be useful for troubleshooting purposes, and I don't believe this is possible with version 1. It would also avoid having to track 2 SDK version changes.
However, there might be reasons to use different SDK versions, which could warrant adding notes to the relevant documentation.
Beta Was this translation helpful? Give feedback.
All reactions