Support AWS Step Functions callback patterns in workflow #2658
Labels
feature-request
A feature should be added or improved.
Comments
|
Sounds great. |
albegali
pushed a commit
to albegali/aws-cdk
that referenced
this issue
May 30, 2019
…ix in resourceArn (aws#2658) * Add waitForTaskToken property to SentToQueue, InvokeFunction, PublishToTopic task types * Add payload parameter to InvokeLambda parameters * Unit test BREAKING CHANGE: InvokeFunction now requires props as second argument
4 tasks
albegali
pushed a commit
to albegali/aws-cdk
that referenced
this issue
Jun 4, 2019
…ix in resourceArn (aws#2658) * Merge awslabs:master into albegali:master * Resolved conflicts
albegali
pushed a commit
to albegali/aws-cdk
that referenced
this issue
Jun 4, 2019
…ix in resourceArn (aws#2658) * InvokeFunction props is now optional * Payload can have multiple nesting levels * Unit test * Integration test * Invoke lambda via SFN integrated service ARN
4 tasks
rix0rrr
pushed a commit
that referenced
this issue
Jun 18, 2019
This PR allows one to work with Task states that implement the callback service integration pattern. Introduces a new class for integrating with Lambda in the new invocation style, since there are a number of subtle differences with the old invocation style. The supported task types are: * `RunLambdaTask` (AWS Lambda) * `SendToQueue` (AWS SQS) * `PublishToTopic` (AWS SNS) Closes #2658, closes #2735.
This was referenced Aug 22, 2019
This was referenced Dec 12, 2019
This was referenced Jan 20, 2020
|
Is it done for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to support Callback patterns in workflow, there is the need to append
.waitForTaskTokenstring toresourceArnfor the following task types:I will submit a PR for this, looking forward to the comments and review.
The text was updated successfully, but these errors were encountered: