New overriden parameter values don't show up in diff
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 53
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
When performing an update, if I provide an override for parameter that did not exist in the old template, but does exist in the new template, that new parameter does not appear in the parameter diff confirmation prompt.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce an update using an override for a parameter absent from the old template but present in the new one. Trace the parameter diff confirmation prompt and compare how old, new, and overridden parameters are collected. Done means the newly introduced overridden parameter appears in the confirmation diff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100