Maintenance: Release version 1.5.0

[hjgraca]

Summary

feat: Idempotency calculate remaining invocation available time as part of the idempotency record

Why is this needed?

In the current implementation of Idempotency we don't have the InProgressExpiration timestamp. So currently if a lambda invocation expired there would be no way to retry it, when using the Idempotent attribute in the lambda handler or Idempotent attribute on another method

This field is required to prevent against extended failed retries when a Lambda function times out, Powertools for AWS Lambda (.NET) calculates and includes the remaining invocation available time as part of the idempotency record.

If a second invocation happens after this timestamp, and the record is marked as INPROGRESS, we will execute the invocation again as if it was in the EXPIRED state (e.g, expire_seconds field elapsed).

This means that if an invocation expired during execution, it will be quickly executed again on the next retry.

Which area does this relate to?

Idempotency

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (.NET) Tenets