Add AWS resource detector entry points

[abstractOwl]

Description

The AWS resource detectors currently are not picked up when using the new OTEL_EXPERIMENTAL_RESOURCE_DETECTORS environment variable because they are not registered under the opentelemetry_resource_detector entry point.

This PR adds the relevant section to the sdk-aws pyproject.toml file to allow the resource detectors to be used.

Fixes #1861, fixes #2370

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Added the following line to my Dockerfile in an otel-instrumented test Flask app:

RUN echo "\n\n[opentelemetry_resource_detector]\naws_elastic_beanstalk =
opentelemetry.sdk.extension.aws.resource.beanstalk:AwsBeanstalkResourceDetector"
 >>
/usr/local/lib/python3.12/site-packages/opentelemetry_sdk_extension_aws-2.0.1.dist-info/entry_points.txt

The logs showed that the relevant resource attributes were set:

web_1             | {
web_1             |     "resource_metrics": [
web_1             |         {
web_1             |             "resource": {
web_1             |                 "attributes": {
web_1             |                     "telemetry.sdk.language": "python",
web_1             |                     "telemetry.sdk.name":
"opentelemetry",
web_1             |                     "telemetry.sdk.version": "1.20.0",
web_1             |                     "cloud.provider": "aws",
web_1             |                     "cloud.platform":
"aws_elastic_beanstalk",
web_1             |                     "service.name": "otel_test",
web_1             |                     "service.instance.id": "abc123",
web_1             |                     "service.namespace": "12345",
web_1             |                     "service.version": "0.0.1",
web_1             |                     "telemetry.auto.version": "0.41b0"
web_1             |                 },
web_1             |                 "schema_url": ""
web_1             |             },
web_1             |             "scope_metrics": [],
web_1             |             "schema_url": ""
web_1             |         }
web_1             |     ]
web_1             | }

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: abstractOwl (d25b6fb, 9bcb2dc)
• ✅ login: lzchen / name: Leighton Chen (c89c974)
• ✅ login: xrmx / name: Riccardo Magliocchetti (53c10df)
• ✅ login: ocelotl / name: Diego Hurtado (d3f9a16)

[wangzlei]

Thanks for contributing the PR. It looks good to me.

[tammy-baylis-swi]

Thank you for picking this one up. I'll trigger the checks.

[abstractOwl]

@tammy-baylis-swi: Thanks! I see that the lint is failing but I'm not sure that it's related to my changes

I also had two quick questions:

1. sdk-extension-aws seems to be published separately from the main sdk based on recent PyPi versions. Should I be updating the changelog if it's not technically part of the next release?
2. What is the process for getting these changes released?

[tammy-baylis-swi]

the lint is failing but I'm not sure that it's related to my changes

Agreed, the same not-context-manager checks are failing on other PRs too after a recent merge. So not from your changes.

What is the process for getting these changes released?

That's a good question. The extension's on the regular release exclude list, and that release history predates my contributions 🙂

I just found another issue from last year saying this package is not released anymore!!: #1899 (comment) Please could you comment on that issue with a link to this PR?

[abstractOwl]

Thanks, I'll comment on that issue! Also wondering whether @wangzlei might have some thoughts as someone (presumably?) working at AWS

[wangzlei]

IMO, the changelog update in this PR is ok, the repo maintainer will manage the remaining work.

There are tow component maintainers. If @NathanielRN is not available, can @Kausik-A help take a look?

[NathanielRN]

LGTM! Thanks for contributing to open source :)

[lzchen]

@NathanielRN

I believe we stopped releasing this package from the regular OpenTelemetry workflow on your request and haven't released it since. Is this extension still being supported, and if so, if we aren't releasing it as part of the regular workflow do we still want to keep it in the opentelemetry repo?

[NathanielRN]

@lzchen

Thanks for asking! This is a useful change and I imagine yes we would want it released. However I don't work on the AWS team that supports anymore and I want to make sure they have a say on its plans 😅

@wangzlei do you know someone who can support the release of this package?

[lzchen]

Merging this for now.

@wangzlei

If these aren't going to be released from this repository anymore, we will probably be discussing in removing it from OpenTelemetry soon.

[srprash]

If these aren't going to be released from this repository anymore, we will probably be discussing in removing it from OpenTelemetry soon.

Similar issue calling out that the project containing these resource detectors is not included in the OTel release cycle. #1899

It is tracked in the AWS backlog but not currently being worked on. cc: @vasireddy99 @vsakaram

@NathanielRN What was the reason for moving this package out of the OTel release? I don't see why we wouldn't want this released in sync with the rest of the packages.

[NathanielRN]

@NathanielRN What was the reason for moving this package out of the OTel release? I don't see why we wouldn't want this released in sync with the rest of the packages.

@srprash this was a request our team made several years ago because we wanted to release it once we knew the release candidate was stable and wouldn't break AWS customers.

I would support joining the release cycle again for automatic release!

[srprash]

@lzchen What would it require to pull this package in the OTel's release cycles? I will be happy to help if you need.

[ocelotl]

I would prefer for this package to be moved out of this repo or integrated with the normal release process.

@NathanielRN @srprash are you ok with either of these options?

[srprash]

integrated with the normal release process.

@ocelotl - I prefer this

[abstractOwl]

Any update here? @ocelotl @lzchen

[lzchen]

Continued discussion here #1899