test(eventBridge): add regression test for content filtering operators in event patterns#729
Open
test(eventBridge): add regression test for content filtering operators in event patterns#729
Conversation
…s in event patterns Verifies that content filtering patterns (prefix, numeric, exists, anything-but) pass through compilation unchanged into the EventPattern property of the generated AWS::Events::Rule resource. The feature was already supported via direct JSON serialisation of the event object — this test guards against a future regression. Closes #513 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a regression test covering EventBridge content filtering operators (
prefix,numeric,exists,anything-but) in event patterns for bothcloudwatchEventandeventBridgeevent sources.Why
Content filtering was reported as missing in #513, but the feature already works — the
eventobject is serialised directly viaJSON.stringifywith no schema restriction on its shape, so all EventBridge content filtering operators pass through unchanged.No test existed to confirm this or guard against a future regression.
Closes #513
Test plan
itParamtest covering bothcloudwatchEventandeventBridgesources withprefix,numeric,exists, andanything-butoperatorsnpm test— 499 passing🤖 Generated with Claude Code