aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Updating root stack adding "notificationARNs" property to child stack does not behave as expected - update ignores this and the property is not applied to the child stack
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::CloudFormation::Stack
### Resource Name
_No response_
### Issue Description
Bug in cloudformation:
Updating root stack adding "notificationARNs" property to child stack does not behave as expected - update ignores this and the property is not applied to the child stack
Seems like the workaround right now is to manually make an out-of-band change to the child stack directly - updating the notificationARNs property that way
### Expected Behavior
updating the root stack will cause the property to be reflected in the child stack
### Observed Behavior
notificationARNs not reflected in child stack at all
### Test Cases
1. Create root stack with child stack
2. update root stack by adding notificationARNs property to child stack in template
3. can observe that the update does not do what is intended - notificationARNs property not updated.
### Other Details
_No response_
Contributor guide
Research direction
Reproduce the issue with a root stack and child stack, then update the root template by adding the notificationARNs property to the child stack. Compare the child stack's notificationARNs before and after the update. Done means the property is reflected in the child stack without an out-of-band change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100