Support the new "Parameters" option of AWS Step Functions
See original GitHub issueAWS Step Functions released support for Parameters option in the input definition.
CDK should be able to define this attribute:
const initalTask = new stepfunctions.Task(this, "InitialTask", {
resource: asyncLambda,
parameters: {
"task.$": "$.task"
}
inputPath: "$",
outputPath: "$.state"
}).next(nextTask);
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Pass Parameters to a Service API - AWS Step Functions
Use the "Parameters" field in a Task state to control what parameters are passed to a service API. Pass Static JSON as Parameters....
Read more >AWS Step Function Tips and Tricks - In Plain English
4 hacks to help construct workflows · 1. Lifting a single value into an Array · 2. Concatenating items into a single array...
Read more >AWS Step function - Field Parameters is not supported in ...
I'm trying to create an AWS Step function, but it is showing an error message as Field Parameters is not supported in the...
Read more >Getting Started with AWS Step Functions | Alex Hyett
More useful is the Parameters option which allows you to construct an object using values from the previous state result. For example, if...
Read more >[Handbook] AWS Step Functions Input and Output ...
Using the Parameters field will help you create a collection of key-value pairs that are all passed as input. These values can be...
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 FreeTop 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
Top GitHub Comments
commit d0c52832ec4df8e49f9ddef4bc8b8032019b54df has removed this… can this issue be reopened?
I could not use the CloudFormation overrides because what I need is a property (on TaskProps) that will end up as a JSON object. I got it to work for now with this: