-
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
EventPattern: JSON Serialization of detail_type is incorrect #16563
Labels
@aws-cdk/aws-events
Related to CloudWatch Events
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
Comments
mickael-caro-sonarsource
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Sep 21, 2021
Are you using the |
rix0rrr
added
the
response-requested
Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
label
Sep 29, 2021
rix0rrr
added a commit
that referenced
this issue
Sep 29, 2021
Hi @rix0rrr yes this is the case. |
github-actions
bot
removed
the
response-requested
Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
label
Oct 1, 2021
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-events
Related to CloudWatch Events
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
While using the aws_events.EventPattern class, cdk output as JSON, for detail_type renders detailType instead of detail-type, which cause the pattern to not match the real payload received from EventBridge.
Reproduction Steps
Create the following event pattern
When issuing a CDK synth, the output eventPattern looks like this :
"EventPattern": {
"account": [
{
"Ref": "AWS::AccountId"
}
],
"detail": {
"Status": [
"Failed",
"TimedOut",
"Cancelled"
]
},
"detailType": [
"EC2 Automation Execution Status-change Notification"
],
"region": [
"eu-central-1"
],
"source": [
"aws.ssm"
]
}
What did you expect to happen?
detailType object should be rendered as detail-type instead.
Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: