You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Paul Hinze 14cea95e86 terraform: another set of ignore_changes fixes ... This set of changes addresses two bug scenarios: (1) When an ignored change canceled a resource replacement, any downstream resources referencing computer attributes on that resource would get "diffs didn't match" errors. This happened because the `EvalDiff` implementation was calling `state.MergeDiff(diff)` on the unfiltered diff. Generally this is what you want, so that downstream references catch the "incoming" values. When there's a potential for the diff to change, thought, this results in problems w/ references. Here we solve this by doing away with the separate `EvalNode` for `ignore_changes` processing and integrating it into `EvalDiff`. This allows us to only call `MergeDiff` with the final, filtered diff. (2) When a resource had an ignored change but was still being replaced anyways, the diff was being improperly filtered. This would cause problems during apply when not all attributes were available to perform the replacement. We solve that by deferring actual attribute removal until after we've decided that we do not have to replace the resource.		10 years ago
..
data_source.go	core: rerun resource validation before plan and apply	10 years ago
provider.go	core: rerun resource validation before plan and apply	10 years ago
provider_test.go	core: Fix issues with ignore_changes	10 years ago
resource.go	terraform: another set of ignore_changes fixes	10 years ago
resource_test.go	terraform: another set of ignore_changes fixes	10 years ago