Maintenance: Refactor Idempotency functional tests with DynamoDB Local

[heitorlessa]

Summary

As of now, writing tests for Idempotency is more costly than creating features or addressing bugs. This is largely due to the complex Boto stubber setup required - it's error prone.

DynamoDB Local official wording also changed to: Except for the endpoint, applications that run with the downloadable version of Amazon DynamoDB should also work with the DynamoDB web service.

This gives us a good trade-off on performance (slower) and contract (closer, not exactly the same).

Why is this needed?

Reduce operational overhead and cognitive load when dealing with tests in Idempotency. Idempotency tests are the hardest to write across the entire code base, and this can lead to future errors as we try to cut corners to overcome the sheer complexity.

Which area does this relate to?

Idempotency

Solution

Use official Docker Image and create new tests with this approach, then recreate one test at a time to prevent regressions.

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

[heitorlessa]

This won't be necessary anymore. We completed E2E refactor and will move Idempotency to the new stack to use the real service to reduce maintenance burden with arrange/act

[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.

[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.