(events): Unable to use content based filtering patterns in detailType

[scub]

Describe the bug

When using the L2 construct for EventBridge Rules a type failure occurs when attempting to create an event bridge rule that uses content based filtering patterns. Requiring the use of a trapdoor in order to achieve the desired results.

Expected Behavior

Content based filtering patterns are supported in an events detailType

Current Behavior

Type '{ prefix: string; }' is not assignable to type 'string'

Reproduction Steps

#!/usr/bin/env node
import 'source-map-support/register';
import * as cdk from 'aws-cdk-lib';
import { Rule, CfnRule } from 'aws-cdk-lib/aws-events';

const app = new cdk.App();

const stack = new cdk.Stack(app, 'RuleTestStack');

const rule = new Rule(stack, 'Rule', {
  eventPattern: {
    detailType: [{"prefix": "shared_"}]
  }
});

Possible Solution

See #30222

Using a trapdoor does provide a work around

(rule.node.defaultChild as CfnRule).addOverride('Properties.EventPattern.detail-type', [{"prefix": "shared_"}])

Additional Information/Context

No response

CDK CLI Version

2.141.0

Framework Version

No response

Node.js Version

18.18.0

OS

OSX

Language

TypeScript

Language Version

Typescript 5.4.0

Other information

No response

[pahud]

Thank you for your PR.

[victorskl]

We hit to similar issue but with source field for us. We went with @ts-ignore for now. It is not an issue at EventBirdge rule side and, accepting it.

// @ts-ignore
source: [{ "anything-but": "orcabus.workflowmanager" }],

[snowe2010]

Same issue here, except we use the java cdk (through Kotlin) and this is thus not resolvable at all due to the typing. On the typescript side we were able to resolve it with // @ts-ignore as well, but we're SOL with the Java CDK.

[ValeriyaIvanovaPolestar]

Same issue for me as well, I am trying to create detail-type filtering like that and I got the same limitation:

detailType: [{ "equals-ignore-case": "Something"}]

+1 vote for this feature 💯