-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Parameters" Parameter for Step Functions Tasks #2735
Labels
feature-request
A feature should be added or improved.
Comments
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
This was referenced Sep 24, 2024
Open
This was referenced Sep 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prior to CDK
0.32.0
, I defined a Step Functions task to invoke a Lambda function passing in a couple of parameters:These parameters included existing data
$
in the Step Functions, as well as introducingstatus = UNKNOWN_CHANNEL
.From CDK
0.32.0
, this is refactored toNow I think I'm no longer able to provide the parameters in this task definition. I've extended the
InvokeFunction
class to workaround thisAm I missing a simpler approach to this? If not, would it be possible to add support for parameters to the
InvokeFunction
class directly, rather than having to extend the class like above?The text was updated successfully, but these errors were encountered: