aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
AWS CLI - Cloudformation update-stack: specify only changed parameters
- 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
AWS::ElasticBeanstalk::Environment
### Description
Currently, if one wants to update a CloudFormation stack from the AWS CLI, one must specify every parameter used by the stack, and set `UsePreviousValue=true` for parameters that should use previous values.
This is cumbersome and impractical in many use cases, where there are many parameters ... typical in how we deployElastic Beanstalk environments with CloudFormation, with many environment variables required by the application. The problem is most significant with CI/CD deployments of new application versions, while avoiding stack drift.
Having to specify tens of parameters just so we can change the application-version to deploy (and maybe the application version description) is so impractical that the developers refuse to do this, and we end up with drifts ... negating the whole point of using CloudFormation.
Perhaps, we can have a catch-all parameter that says --UsePreviousValuesUnlessSpecified (or something to that effect)
### Other Details
https://stackoverflow.com/questions/61887550/is-there-a-way-to-specify-only-changed-parameters-using-aws-cloudformation-updat
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. Start by reviewing CloudFormation update-stack parameter behavior and the linked Stack Overflow discussion. Done means defining an accepted way to update only changed parameters without supplying every existing parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100