You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(core): configure SNS topics to receive stack events on the Stack construct (#30551)
### Issue # (if applicable)
#8581.
### Reason for this change
It is easier and clearer to specify the SNS Topic ARNs on the stack construct itself instead of passing it as a command line argument.
### Description of changes
Added a new optional stack prop, `notificationArns`, that is written to the CloudAssembly and concatenated with the CLI option `--notification-arns`.
When I added CLI integ tests, I discovered that the existing framework is unable to use your local code. It always retrieves the latest release, which is not what you want when running it locally. This fixes that.
Don't forget to select stacks by hierarchical ID (currently display name, in our tests) when writing certain test code. Otherwise, the tests may not select the stack you expected.
### Description of how you validated changes
Unit tests + CLI integ 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*
integTest('context in stage propagates to top',withDefaultFixture(async(fixture)=>{
190
+
// bootstrapping also performs synthesis. As it turns out, bootstrap-stage synthesis still causes the lookups to be cached, meaning that the lookup never
191
+
// happens when we actually call `cdk synth --no-lookups`. This results in the error never being thrown, because it never tries to lookup anything.
192
+
// Fix this by not trying to bootstrap; there's no need to bootstrap anyway, since the test never tries to deploy anything.
193
+
integTest('context in stage propagates to top',withoutBootstrap(async(fixture)=>{
191
194
awaitexpect(fixture.cdkSynth({
192
195
// This will make it error to prove that the context bubbles up, and also that we can fail on command
0 commit comments