You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just noticed that the State.EnteredTime in the context object has a differently formatted timestamp compared to what's in the AWS service or in stepfunctions-local.
This mismatch of formats can also be observed between Execution.StartTime and State.EnteredTime, where the former is correct.
I only noticed this because we use State.EnteredTime as an "updated_at" attribute in our DynamoDB records.
Using the example below, the parsed output we receive is:
Is there an existing issue for this?
Current Behavior
I just noticed that the
State.EnteredTime
in the context object has a differently formatted timestamp compared to what's in the AWS service or in stepfunctions-local.This mismatch of formats can also be observed between
Execution.StartTime
andState.EnteredTime
, where the former is correct.I only noticed this because we use
State.EnteredTime
as an "updated_at" attribute in our DynamoDB records.Using the example below, the parsed output we receive is:
Note the granularity of the sub-second element, and the timezone offset notation.
Expected Behavior
The date formats should match for both context attributes:
How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
Create state machine
Start an execution
Describe execution
Environment
Anything else?
For readability, this is the state machine definition used in the above example:
The text was updated successfully, but these errors were encountered: