Fix for parent-child state machine calls #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
This PR allows adding
-stepFunctionsEndpoint
argument when starting Step Functions Local.Background:
Been using serverless-step-functions-local and it's working well locally for individual state machine runs.
However, when running a step machine that calls another step machine as a task, I'm getting this error message:
{"Type":"ExecutionFailed","PreviousEventId":5,"ExecutionFailedEventDetails":{"Error":"StepFunctions-AWSStepFunctionsException","Cause":"The security token included in the request is invalid. (Service: AWSStepFunctions; Status Code: 400; Error Code: UnrecognizedClientException; Request ID: 72e40098-51a3-4a15-83b4-0d30b57c0f56; Proxy: null)"}}
(Note:
--endpoint-url http://localhost:8083
was specified when running theaws stepfunctions
command)Adding the
-stepFunctionsEndpoint
argument withhttp://localhost:8083
as the value did the trick and executed the child state machines.Next Step: Pass the
stepFunctionsEndpoint
from serverless-step-functions-local index.js#L96-L101