(aws-stepfunctions-tasks): StepFunctionsStartExecution accepts invalid input type
See original GitHub issueStepFunctionsStartExecution supports an input
argument of type TaskInput. If I pass in a value which is not of type TaskInput
, CDK successfully built and deployed the Step Functions task, but ignored the input argument. In other words, a CloudFormation template was generated and deployed, but the task input was not included in the template.
Reproduction Steps
new StepFunctionsStartExecution(this, 'ExampleStateMachineStartExecution', {
input: TaskInput.fromDataAt('$.exampleJsonPath').value,
stateMachine: 'example-state-machine',
});
What did you expect to happen?
CDK raises an error at build time because TaskInput.fromDataAt('$.exampleJsonPath').value
is not of type TaskInput
.
What actually happened?
CDK successfully built and deployed the stack. input
was not included in the generated CloudFormation template.
Environment
- CDK Version : 1.75.0
- Language (Version): TypeScript (3.7.5)
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
class StepFunctionsStartExecution (construct ... - Amazon.com
The Step Functions state machine to start the execution on. associateWithParent? boolean, Pass the execution ID from the context object to the execution...
Read more >aws step function choice invalid path - Stack Overflow
Try $.Payload.input . My guess is that Variable applies to the original object, not to the output of your lambda function. – ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.
It appears the same problem arises in
LambdaInvoke
, which usesTaskInput
for itspayload
property.