aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

CloudFormation Git sync - Nested stacks

Open
#1,898 2 comments 2 reactions 0 assignees View on GitHub
bug
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

We have enabled CloudFormation Git sync on our root template.

Layout
- src
|- root.yaml
| - ecs.yaml
- deploy.yaml

Ofcourse there are more files in this repo but that is not important for this example

The ecs.yaml is included via nested stack from root.yaml

### Expected Behavior

When ecs.yml changes and is pushed to the monitored branch I expect that this file will be processed by Cloudformation to change resources.

### Observed Behavior

- make a change in ecs.yaml
- Push it to the branch
- See Cloudformation start the update process
- See that the ecs stack is also performing the "update"
- Looking on the "template" tab for ecs, I see an old version of the ecs template
- No resources in ecs.yaml or underlying stacks get update.

### Test Cases

- Configure git sync on an existing repo with nesting stacks
- Update a nested stack template file
- Push to branch
- See nothing changing.

### Other Details

This was on already existing stack

Contributor guide

Open the contributing guide

Research direction

Start with src/root.yaml, src/ecs.yaml, and deploy.yaml to verify how the nested stack is referenced. Reproduce the change on the monitored branch through CloudFormation Git sync, then confirm that the nested template and its underlying resources update to match ecs.yaml.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.