Nested StateMachine startExecution.sync:2 is not supported in Local StepFunction docker image

[xbeta]

This is a (Bug Report)

Description

For bug reports:

• What went wrong?
  • startExecution.sync:2 is not supported in Local StepFunction docker image
• What did you expect should have happened?
  • sync:2 is working and same behavior as the StepFunctions in AWS console
• What was the config you used?

{
  "Comment": "Hello World Main",
  "StartAt": "HelloWorldMain",
  "States": {
    "HelloWorldMain": {
      "Type": "Task",
      "Resource": "arn:aws:states:::states:startExecution.sync:2",
      "HeartbeatSeconds": 60,
      "Parameters": {  
        "StateMachineArn":"arn:aws:states:us-west-2:661617860809:stateMachine:HelloWorld",
        "Input": {  
          "Comment":"Hello world!",
          "AWS_STEP_FUNCTIONS_STARTED_BY_EXECUTION_ID.$": "$$.Execution.Id"
        }
      },
      "End": true
    }
  }
}

• What stacktrace or error message from your provider did you see?

2021-01-16 00:20:41.265: arn:aws:states:us-east-1:123456789012:execution:ApplicationApproval-Dev:460b67cc-a770-4e47-a78d-b04d14cb8712 : {"Type":"ExecutionFailed","PreviousEventId":24,"ExecutionFailedEventDetails":{"Error":"States.Runtime","Cause":"An error occurred while scheduling the state 'ApplicationScreeningWorkflow'. The provided ARN 'arn:aws:states:us-east-1:123456789012:states:startExecution.sync:2' is invalid."}}
Execution ARN: 

For feature proposals:

• What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.
• If there is additional config how would it look

Similar or dependent issues:

• None

Additional Data

• Serverless Framework Core Version you're using:
• The Plugin Version you're using:
• Operating System:
• macOS 10.15
• Stack Trace:
• Provider Error messages:

[theburningmonk]

@xbeta if the problem is with step functions local then this is the wrong place to raise the issue as that's outside our control. This plugin just lets you configure your state machines in the serverless.yml, we don't maintain the local step functions docker imgae.

[xbeta]

@xbeta if the problem is with step functions local then this is the wrong place to raise the issue as that's outside our control. This plugin just lets you configure your state machines in the serverless.yml, we don't maintain the local step functions docker imgae.

Thanks Actually I came here because AWS StepFunctions support told me to come here and file a public ticket.

Do you have other places to suggest to file such public ticket to AWS ?

[theburningmonk]

I see. Happy to keep the ticket there if they need to track the issue somewhere. Some of the AWS projects have public repos (like AWS SAM) but a lot don't, I don't recall seeing any public repo for Step Functions local. The closest thing to a public ticket is if you post a ticket in the AWS forum

[xbeta]

@theburningmonk Sure, but again, I just follow what the AWS Support Engineer suggest me. I think this feature is specially important for those that want to develop locally and match what's in AWS Console.