-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
StepFunctions -> TaskInput cannot select the entire Input #6388
Comments
This seems to be a fundamental limitation of StepFunctions itself, and not necessarily the CDK. Based on their documentation, they're using JsonPath. I can't seem to find a way in JsonPath to specify a 'select all' operator. The closest that comes is the Can you try the |
Also, in case of the |
@nija-at StepFunctions is perfecty happy with a @rix0rrr That's good to know, thanks 👍 I still believe the JsonPath parser isnt't correct though, as There is another work around as well, but it's not obvious to find:
|
@rix0rrr - However, I seem to have missed in the documentation that The validations in field.ts will need to updated to support aws-cdk/packages/@aws-cdk/aws-stepfunctions/lib/fields.ts Lines 131 to 140 in 983dd40
|
'$' is a valid reference path that indicates that the entire object should be selected. '$$' is a valid selection of the context object that indicates that the entire context object should be selected. fixes #6388
'$' is a valid reference path that indicates that the entire object should be selected. '$$' is a valid selection of the context object that indicates that the entire context object should be selected. fixes #6388 Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Using
TaskInput
in step functions, it is impossible to select the entire step input.I would expect to be able to select the entire input using
$
, however the JSON path validator expects a path to start with$.
Reproduction Steps
In a newly created project, put this as stack:
Error Log
Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: