Create and Delete actions for output plans #27512
Conversation
The planning logic here was inspired by resources, but unlike resources a null value is valid for an output and does not necessarily indicate it is being removed. If both before and after are null, the change should be NoOp. When an output is removed from the configuration, we have a separate node to create a Delete action to remove it from the state.
Codecov Report
|
jbardin
force-pushed
the
jbardin/output-plans
branch
from
d8d982c to
ed981c5
Compare
Rather than using a prior value of null to indicate create, which is imprecise because null is a valid output value, only plan values that didn't exist in the prior state as Create changes.
jbardin
force-pushed
the
jbardin/output-plans
branch
from
ed981c5 to
191124e
Compare
|
Would this fix be backported to the next Terraform 0.14 release (e.g: 0.14.6)? It is already listed as a fix on the |
|
Hi @alloveras, This wasn't immediately backported because it wasn't a critical issue blocking any 0.14 functionality. Thanks! |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked as resolved and limited conversation to collaborators
The planning logic here was inspired by resources, but unlike resources
a null value is valid for an output and does not necessarily indicate it
is being removed. If both before and after are null, the change should
be NoOp. When an output is removed from the configuration, we have a
separate node to create a Delete action to remove it from the state.
Rather than using a prior value of null to indicate Create, which is
imprecise because null is a valid output value, only plan values that
didn't exist in the prior state as Create changes.
Fixes #27490