-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/datadogexporter] Migrating datadog exporter to use aws sdk v2 #36797
base: main
Are you sure you want to change the base?
Conversation
if err != nil { | ||
return nil, err | ||
} | ||
return &Provider{ | ||
logger: logger, | ||
detector: ec2provider.NewProvider(sess), | ||
detector: ec2provider.NewProvider(cfg), |
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.
The datadogexporter depends on the NewProvider function from metadataproviders, and the resourcedetectionprocessor also relies on the same function.
@LZiHaN can you fix the merge conflict? Otherwise the tests won't run |
# Conflicts: # internal/metadataproviders/go.mod
done. |
Looks like there are some linting errors, could you take a look at those? |
…ollector-contrib into migrate-to-sdk-v2
I’ve addressed the linting errors and tested everything locally. Please feel free to let me know if there’s anything else I should take a look at! |
Description
Migrating datadog exporter to use aws sdk v2
Link to tracking issue
refer to #36699
Testing
passes tests.
updated mock client implementations to support the new SDK interfaces.
Documentation
no need to update.