-
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
[aws-stepfunctions-tasks] Problem with mapping a boolean and a number from an input event in a step function to insert into dynamodb #9007
Comments
@michaelbrewer - I'll need to dig into the boolean case a bit more, will take a look a bit later today |
Yes, thank you @shivlaks - I looked at some of the tests and ascertained that is the way to do it.
works great... Please let me know if you have something on booleans as I can't find an example mapping a boolean in the tests. |
@michaelwiles are you attempting to set a boolean based on state input (by selecting part of the path?) we might need to add a |
Yes, that's what I am doing - and that's what is needed -> "booleanFromJsonPath" |
@shivlaks I've created a pull request for this though it's going to need a bit more attention as I don't think I've followed the process properly. |
@michaelwiles took a quick glance and provided some feedback. let me know if you're running into any issues iterating. |
thank you. will follow up |
…e input (Json path) (#9088) It is now possible to map a boolean value from state input using a Json path. function booleanFromJsonPath added to DynamoAttributeValue which accepts a Json path Closes #9007 Co-authored-by: Michael Wiles <michaelwiles@lumkani.com> Co-authored-by: Shiv Lakshminarayan <shivlaks@amazon.com>
…e input (Json path) (aws#9088) It is now possible to map a boolean value from state input using a Json path. function booleanFromJsonPath added to DynamoAttributeValue which accepts a Json path Closes aws#9007 Co-authored-by: Michael Wiles <michaelwiles@lumkani.com> Co-authored-by: Shiv Lakshminarayan <shivlaks@amazon.com>
So thank you for upgrading the dynamodb integration from step functions.
I'm now starting to use it.
Firstly, when doing this - the recommended way to map values in a step function:
"alarm_id": DynamoAttributeValue.from_number(JsonPath.number_at("$.detail.alarm_id")),
This is synthesized as "alarm_id":{"N":"-1.8881545897087864e+289"}}
Very weird. Especially since that is what is actually deployed...
Surely that should be
"alarm_id":{"N.$":"$.detail.alarm_id"}}
Then what about when I want to map a boolean?
There is no boolean_at in JsonPath...
So what I really want to know is why access to the constructor of DynamoAttributeValue is not provided because this would solve all my problems...
The text was updated successfully, but these errors were encountered: