Maintenance: fix idempotency e2e tests

[dreamorosi]

Summary

After merging #2570 some of the integration tests related to the Idempotency utility are failing.

This is because some of the payloads used to seed the tests don't match the control idempotency key due to the former not being deep sorted.

This was raised during the review but I forgot to ask the contributor to include it before merging.

Why is this needed?

So that we can continue running integration tests.

Which area does this relate to?

Tests

Solution

We should make sure that all the payloads in the packages/idempotency/tests/e2e/makeIdempotent.test.ts file are sorted.

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 ⚠️

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.