Feature enhancement: Create a Subsegments for operations handled by Powertools about powertools-lambda-java HOT 5 OPEN

Good idea but the idempotency module works before and after the handler method is actually executed.
Should we add 2 segments?

• One before when we check in the DB if the idempotency key is already there or insert it
• One after when we update the record

from powertools-lambda-java.

Also, we may have a "dependency" issue. This should happen only if tracing is enabled / powertools-tracing is used. But we don't want to add a (maven) dependency to xray / powertools-tracing in the idempotency module...

from powertools-lambda-java.

Let's do this in v2

from powertools-lambda-java.

Idempotency isn't the only module that calls AWS services. Do we want to add it to everything (e.g. the various params?)

Also, we may have a "dependency" issue. This should happen only if tracing is enabled / powertools-tracing is used. But we don't want to add a (maven) dependency to xray / powertools-tracing in the idempotency module...

This will be the trick.

from powertools-lambda-java.

@heitorlessa wdyt?

from powertools-lambda-java.