-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
lambda-eventsources: DynamoDB, unable to filter for bool values #30734
Comments
Hi @bpauwels , thanks for reaching out. I checked the passage of boolean value and you seem to be correct in saying it does not accept Boolean values.
|
What a luck, just tried to use filter for boolean and there is already a bug. 🍀 |
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
…ws#31011) ### Issue # (if applicable) Closes aws#30734 ### Reason for this change Filtering on boolean values was not possible ### Description of changes `lambda.FilterRule.isEqual(...)` now accepts `boolean` values ### Description of how you validated changes Added a unit test and integration test ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Describe the bug
When I add a lambda-eventsource to a dynamodb stream, I cannot filter for bool values because the .isEqual() function only allows string parameters.
Expected Behavior
Possibility to filter for all DynamoDB data types.
Current Behavior
.isEqual() only takes string parameters
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.140.0
Framework Version
No response
Node.js Version
22.1.0
OS
MacOS 14.2.1
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: