aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Feature Request - AWS CloudFormation Git sync
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
Other
### Resource name
CloudFormation Git sync
### Description
While using the new feature of CloudFormation Git sync it will update the stack when there is a push/merge in the code and then it creates the ChangSet and Executes the changes automatically.

**From the document:**
When you commit changes to the template or the deployment file, CloudFormation automatically updates the stack[1]
**Feature Request to the team:**
Instead of automatically Updating the stack (executing ChangeSet) can we have a new functionality where user can execute the ChangeSet so that they can check if the update on the CloudFormation template will trigger any replacement update or modify when using GitSync.
This can be very helpful for stacks which are in production environment
Reference:
[1] Working with AWS CloudFormation Git sync
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/git-sync.html
### Other Details
_No response_
### Other Details
_No response_
Contributor guide
Research direction
The issue provides no repository files or tests. Start with the linked AWS CloudFormation Git sync documentation and the described automatic ChangeSet execution behavior; clarify the review and manual-execution workflow required before implementation. Done would be an agreed product and implementation scope for production-safe updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, git
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100