-
Notifications
You must be signed in to change notification settings - Fork 88
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
Feature Request: Add support for ResultSelector #95
Comments
Anny chance this could be pushed through? Seems like the linked PR for this is almost ready? |
@a13zen We're taking another look at the PR to get this shipped soon. Sorry for the delay! |
Unfortunately I see that last activity here was a year ago, any chance this is getting implemented? |
For anyone else coming here looking for a solution until this is implemented, I found a workaround that works for me. lambda_run_step = LambdaStep(
state_id="lambda_run_step",
parameters={
"FunctionName": "db_run_procedure",
"Payload": {
"name": "helloworld",
"schema": "dummy",
"database": "example"
}
}
)
lambda_run_output_step = Pass(
state_id="lambda_run_output_step ",
parameters = {
"lambda_run_result.$": "$.Payload"
}
) |
ResultPath is supported in the SDK, but the newer ResultSelector is not which is preferrable for Lambda functions which emit a bunch of metadata in addition to the JSON output result.
See docs
The text was updated successfully, but these errors were encountered: