Describe the bug

A change was introduced in v2.160.0 which appears to be wiping the notificationARNs property on a CloudFormation stack when cdk deploy is run against an existing stack with that property set. This represents a regression on previous behaviour.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

2.159.1

Expected Behavior

cdk deploy does not modify the notificationARNs property on existing deployed stacks

Current Behavior

cdk deploy wipes the notificationARNs property where it is set on existing deployed stacks

Reproduction Steps

Deploy a stack. Modify the notificationARNs property outside of CDK. Then deploy a subsequent update via cdk deploy

Possible Solution

No response

Additional Information/Context

We have an internal tooling platform which stacks can be registered with in order to provide deployment updates. In order to do this, the tool sets the notificationARNs property on the stack to listen to stack updates via SNS. Previously updating these stacks via cdk deploy did not conflict with that, but it does in recent versions.

CDK CLI Version

v2.167.1

Framework Version

No response

Node.js Version

18

OS

Mac OS

Language

TypeScript

Language Version

5.x

Other information

No response