fix cfngin diff output lookup resolution when no stack change #208
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why This Is Needed
Outputs are not being set on the
Stack
object fromContext
if the CFN stack reports no change. This causes anyoutput
lookups to fail. Output lookups work fine when when the stack being referenced reports changes.What Changed
Fixed
runway plan
for cfngin modules will now properly resolve output lookups when the original stack did not changeScreenshots