Do ignore changes processing again after plan, in case strange things are done during plan that should not be
This commit is contained in:
parent
2e5a8c0f6e
commit
96d84da032
|
@ -214,6 +214,12 @@ func (n *EvalDiff) Eval(ctx EvalContext) (interface{}, error) {
|
|||
plannedNewVal := resp.PlannedState
|
||||
plannedPrivate := resp.PlannedPrivate
|
||||
|
||||
plannedNewVal, ignoreChangeDiags = n.processIgnoreChanges(priorVal, plannedNewVal)
|
||||
diags = diags.Append(ignoreChangeDiags)
|
||||
if ignoreChangeDiags.HasErrors() {
|
||||
return nil, diags.Err()
|
||||
}
|
||||
|
||||
if plannedNewVal == cty.NilVal {
|
||||
// Should never happen. Since real-world providers return via RPC a nil
|
||||
// is always a bug in the client-side stub. This is more likely caused
|
||||
|
|
Loading…
Reference in New Issue