-
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/awss3] Move encodings to extensions #30554
Comments
Pinging code owners for exporter/awss3: @atoulme @pdelewski. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Removing |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
**Description:** Add encoding extension support to AWS S3 exporter. **Link to tracking Issue:** Fixes #30554 **Testing:** Unit tests. **Documentation:** README.
Component(s)
exporter/awss3
Is your feature request related to a problem? Please describe.
The aws s3 exporter has encodings directly listed under it, they should each be moved to a separate extension. The exporter should then allow any encoding extension to be registered against it.
Describe the solution you'd like
as above
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: