Maintenance: consolidate IdempotencyHandler implementation

[dreamorosi]

Summary

The Idempotency utility heavily relies on a class called IdempotencyHandler. This component contains the implementation for the idempotency logic and is expected to be used by all other Idempotency frontends (aka higher-order function, middleware, decorators).

Currently the Middy middleware implementation for Idempotency doesn't use the IdempotencyHandler class fully, which causes some of the logic being duplicated. This tech debt was assumed because the IdempotencyHandler was modelled after the Python implementation, which didn't take in account the Middy lifecycle.

Why is this needed?

To reduce tech debt and avoid code duplication, which converts in maintenance overhead.

Which area does this relate to?

Idempotency

Solution

Modify the IdempotencyHandler so that it exposes more granular methods that will allow the Middy middleware to offer idempotency according to its programming model, without having to reimplement the same logic.

Acknowledgment

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

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.

[github-actions]

This is now released under v1.13.0 version!