Maintenance: Deprecate tracing.base.BaseProvider

[roger-zhangg]

Why is this needed?

In PR #2342 we are providing a observability provider friendly tracing provider to deprecate the current X-Ray specific provider tracing.base.baseprovider and tracing.base.BaseSegment. This new provider solution will enable our customer to send traces to Third party observability provider with ease. After #2342 is merged, the current provider will no longer be used in Tracer.

Which area does this relate to?

Tracer

Solution

This Deprecation is straightforward. This provider class is mostly for internal purpose and X-ray only. If there are customers developing their own provider based on this base provider, they will be able to migrate to the new provider proposed in #2342 with few method/class name changes

Acknowledgment

• This request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[rubenfonseca]

Thank you for opening this @roger-zhangg ! Adding tags to track it for Powertools v3

[leandrodamascena]

We won't deprecate those classes in V3. We will keep as is but instead we'll open doors to new providers.

We can plan to remove this in V4, but wee ned to plan this in advanced.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.