-
Notifications
You must be signed in to change notification settings - Fork 4
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
chore: notice for https://github.com/aws/aws-cdk/issues/28520 #372
Conversation
data/notices.json
Outdated
"components": [ | ||
{ | ||
"name": "aws-cdk-lib/aws-event.EventBus", | ||
"version": "2.117.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only version 2.117 affected?
data/notices.json
Outdated
{ | ||
"title": "(aws-events): EventBus fails because of change to logical id without modifiying the statement id", | ||
"issueNumber": 28520, | ||
"overview": "#27340 introduced the ability to create multiple event bus policies on a single event bus. To facilitate this, the logical Id was changed from \"Policy\" to the statementId. This triggers a replacement, which fails in CloudFormation because the statement ID does not change.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#27340 isn't going to mean anything to the people who view this (when they cdk synth their apps). can you rewrite this overview to be self-sufficient
data/notices.json
Outdated
@@ -423,6 +423,18 @@ | |||
} | |||
], | |||
"schemaVersion": "1" | |||
}, | |||
{ | |||
"title": "(aws-events): EventBus fails because of change to logical id without modifiying the statement id", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is what everyone who uses EventBus is going to see. Is it true that all users will see a failure? Because that is what this title is implying to me.
Co-authored-by: Kaizen Conroy <[email protected]>
Notice for #28520