Skip to content

Maintenance: align timestamp formats for expiration and in_progress_expiration in idempotency table #2298

Closed
@RaphaelManke

Description

@RaphaelManke

Expected Behaviour

I'd expect that the values expiration and in_progress_expiration are using the same timestamp format

Current Behaviour

expiration uses float numbers
in_progress_expiration uses integer

{
 "id": "idempotency-powertools#jpdq6YAEvK9dodm3xTODpA==",
 "data": {
  "customerId": "111",
  "notificationId": "1072d969-8277-4d7c-b95b-abd716add0eb",
  "orderId": "ABC"
 },
 "expiration": 1711981471.834,
 "in_progress_expiration": 1711978111637,
 "status": "COMPLETED"
}

Code snippet

See docs examples.

Steps to Reproduce

  • Add Idempotency
  • Look at the dynamodb table

Possible Solution

No response

Powertools for AWS Lambda (TypeScript) version

latest

AWS Lambda function runtime

20.x

Packaging format used

npm

Execution logs

No response

Metadata

Metadata

Assignees

Labels

confirmedThe scope is clear, ready for implementationenhancementPRs that introduce minor changes, usually to existing featuresgood-first-issueSomething that is suitable for those who want to start contributingidempotencyThis item relates to the Idempotency Utility

Type

No type

Projects

Status

Shipped

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions