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

[AWS components] aws-sdk-go v1 usage should be upgraded to v2 #33208

Open
19 tasks
crobert-1 opened this issue May 23, 2024 · 14 comments
Open
19 tasks

[AWS components] aws-sdk-go v1 usage should be upgraded to v2 #33208

crobert-1 opened this issue May 23, 2024 · 14 comments

Comments

@crobert-1
Copy link
Member

Component(s)

No response

Describe the issue you're reporting

From the AWS SDK for Go README:

We announced the upcoming end-of-support for AWS SDK for Go (v1). We recommend that you migrate to AWS SDK for Go v2.

Here are components that directly depend on it from a search that I'm not 100% confident in:

  • extension/observer/ecsobserver
  • processor/resourcedetectionprocessor
  • internal/metadataproviders
  • internal/kafka
  • internal/aws/cwlogs
  • internal/aws/proxy
  • internal/aws/awsutil
  • internal/aws/k8s
  • internal/aws/xray/testdata/sampleapp
  • internal/aws/xray
  • receiver/awsxrayreceiver
  • receiver/awsecscontainermetricsreceiver
  • receiver/awscontainerinsightreceiver
  • receiver/awscloudwatchreceiver
  • exporter/awss3exporter
  • exporter/awscloudwatchlogsexporter
  • exporter/awsxrayexporter
  • exporter/awsemfexporter
  • exporter/datadogexporter
Copy link
Contributor

Pinging code owners for extension/observer/ecsobserver: @dmitryax @rmfitzpatrick. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for processor/resourcedetection: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for internal/metadataproviders: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for internal/kafka: @pavolloffay @MovieStoreGuy. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for exporter/awsxray: @wangzlei @srprash. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for exporter/awscloudwatchlogs: @boostchicken @bryan-aguilar @rapphil. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for receiver/awsxray: @wangzlei @srprash. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for receiver/awsecscontainermetrics: @Aneurysm9. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for exporter/awss3: @atoulme @pdelewski. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for exporter/awsemf: @Aneurysm9 @shaochengwang @mxiamxia @bryan-aguilar. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for internal/aws: @Aneurysm9 @mxiamxia. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for exporter/datadog: @mx-psi @dineshg13 @liustanley @songy23 @mackjmr. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for receiver/awscloudwatch: @schmikei. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for receiver/awscontainerinsight: @Aneurysm9 @pxaws. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1 crobert-1 added the comp:aws AWS components label Jun 21, 2024
@crobert-1 crobert-1 added never stale Issues marked with this label will be never staled and automatically removed and removed needs triage New item requiring triage labels Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant