terraform/plans/objchange
Martin Atkins 31a4b44d2e backend/local: treat output changes as side-effects to be applied
This is a baby-step towards an intended future where all Terraform actions
which have side-effects in either remote objects or the Terraform state
can go through the plan+apply workflow.

This initial change is focused only on allowing plan+apply for changes to
root module output values, so that these can be written into a new state
snapshot (for consumption by terraform_remote_state elsewhere) without
having to go outside of the primary workflow by running
"terraform refresh".

This is also better than "terraform refresh" because it gives an
opportunity to review the proposed changes before applying them, as we're
accustomed to with resource changes.

The downside here is that Terraform Core was not designed to produce
accurate changesets for root module outputs. Although we added a place for
it in the plan model in Terraform 0.12, Terraform Core currently produces
inaccurate changesets there which don't properly track the prior values.

We're planning to rework Terraform Core's evaluation approach in a
forthcoming release so it would itself be able to distinguish between the
prior state and the planned new state to produce an accurate changeset,
but this commit introduces a temporary stop-gap solution of implementing
the logic up in the local backend code, where we can freeze a snapshot of
the prior state before we take any other actions and then use that to
produce an accurate output changeset to decide whether the plan has
externally-visible side-effects and render any changes to output values.

This temporary approach should be replaced by a more appropriately-placed
solution in Terraform Core in a release, which should then allow further
behaviors in similar vein, such as user-visible drift detection for
resource instances.
2020-05-29 07:36:40 -07:00
..
action.go backend/local: treat output changes as side-effects to be applied 2020-05-29 07:36:40 -07:00
all_null.go configs/configschema: Introduce the NestingGroup mode for blocks 2019-04-10 14:53:52 -07:00
compatible.go don't assert set block length with unknowns 2019-07-12 16:48:49 -04:00
compatible_test.go don't assert set block length with unknowns 2019-07-12 16:48:49 -04:00
doc.go
lcs.go plans/objchange: LongestCommonSubsequence 2018-10-16 19:14:11 -07:00
lcs_test.go plans/objchange: LongestCommonSubsequence 2018-10-16 19:14:11 -07:00
normalize_obj.go configs/configschema: Introduce the NestingGroup mode for blocks 2019-04-10 14:53:52 -07:00
normalize_obj_test.go plans/objchange: Don't panic when dynamic-typed attrs are present 2019-03-11 08:18:26 -07:00
objchange.go configs/configschema: Introduce the NestingGroup mode for blocks 2019-04-10 14:53:52 -07:00
objchange_test.go don't add empty blocks in ProposedNewObject 2019-03-02 11:21:59 -05:00
plan_valid.go configs/configschema: Introduce the NestingGroup mode for blocks 2019-04-10 14:53:52 -07:00
plan_valid_test.go plans/objchange: Don't panic when prior state contains nested map blocks 2019-03-18 09:16:50 -07:00