AWS Step Functions emits EventBridge events on execution state changes (docs here). This is particularly useful when kicking off other tasks when an execution starts or fails, and there's no way to currently test this functionality locally.
Approach
Step Functions Local itself does not seem to support this functionality, but we can infer the state changes from the logs and fire the respective events.
The event details aren't fully implemented:
startDate for all events except ExecutionStarted
There's no information on a specific log line on when the execution started. It can only populate stopDate for these end states.
input and output
There's some logic involved in whether the details are shown (docs here). But if there's a feature request for this information it shouldn't be impossible to implement.
Purpose
AWS Step Functions emits EventBridge events on execution state changes (docs here). This is particularly useful when kicking off other tasks when an execution starts or fails, and there's no way to currently test this functionality locally.
Approach
Step Functions Local itself does not seem to support this functionality, but we can infer the state changes from the logs and fire the respective events.
The event details aren't fully implemented:
startDate
for all events exceptExecutionStarted
There's no information on a specific log line on when the execution started. It can only populatestopDate
for these end states.input
andoutput
There's some logic involved in whether the details are shown (docs here). But if there's a feature request for this information it shouldn't be impossible to implement.