aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
SSM Dynamic Reference Change not detected
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
When using SSM Dynamic references, if the reference or resolved value changes, cloudformation does not detect the change and will not update the stack.
Scenario 1: changing {{resolve:ssm:/dev/pipeline/GitHubOwner}} to {{resolve:ssm:/production/pipeline/GitHubOwner}} in the template
Scenario 2: changing {{resolve:ssm:/dev/pipeline/GitHubOwner:10}} to {{resolve:ssm:/dev/pipeline/GitHubOwner:11}} in the template
Scenario 3: changing the value of the parameter without changing the template (using new 'latest' functionality)
I would expect all three scenarios to be recognized as a change and allow the stack to be updated, instead I get
"No changes to deploy. Stack production-pipeline is up to date"
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. Start by reproducing the three SSM Dynamic Reference scenarios described in the report; the work is done when changes to the reference path, version, and resolved parameter value are all detected as stack changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100