1 Answer
- Newest
- Most votes
- Most comments
1
Would jsonpath logic applied to "interests" payload in the example below achieve what you are after? https://aws.amazon.com/blogs/compute/using-jsonpath-effectively-in-aws-step-functions/
Adding this blog about the Data Flow Simulator that you might find useful as well for your testing. https://aws.amazon.com/blogs/compute/modeling-workflow-input-output-path-processing-with-data-flow-simulator/
answered 2 years ago
Relevant content
- asked 2 months ago
- asked a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
Thank you for your answer. This is exactly what I need. I was trying the filter expression within dataflow-simulator previously, but I failed to produce the result, than I red the ResourcePath limitation, and thought it is global for all AWS json path implementation. But fortunately not. So the real issue with my filter exrpression was about quoting:
$.UserAttributes[?(@.Name=='email')].Value
$.UserAttributes[?(@.Name==email)].Value
In the original jsonpath filter operations string literals must be enclosed by single or double quotes. In AWS you can't use quotes. This is a bit confusing, and would be nice to have highlighted in the AWS documentations.