terraform/states/statefile
James Bardin f915c5d957 remove EachMode from resource state
Due to the fact that resources can transition between each modes, trying
to track the mode for a resource as a whole in state doesn't work,
because there may be instances with a mode different from the resource
as a whole. This is difficult for core to track, as this metadata being
changed as a side effect from multiple places often causes core to see
the incorrect mode when evaluating instances.

Since core can always determine the correct mode to evaluate from the
configuration, we don't need to interrogate the state to know the mode.
Once core no longer needs to reference EachMode from states, the
resource state can simply be a container for instances, and doesn't need
to try and track the "current" mode.
2020-04-30 09:22:14 -04:00
..
testdata/roundtrip states/version3 upgrade: revert provider FQN changes (#24504) 2020-04-06 09:24:23 -07:00
diagnostics.go
doc.go
file.go states/statefile: Tolerate nil state in statefile.New 2018-10-16 19:14:11 -07:00
marshal_equal.go command: Allow tests to run to completion without panics or hangs 2018-10-16 19:14:11 -07:00
read.go command: Fix TestInit_getProvider 2018-11-12 15:19:55 -08:00
roundtrip_test.go read+write the new dependencies in the statefile 2019-11-07 17:49:03 -05:00
version0.go
version1.go
version1_upgrade.go
version2.go states/statefile: decode backend hash as uint64 2019-05-28 23:59:36 +09:00
version2_upgrade.go
version3.go
version3_upgrade.go Mildwonkey/tests (#24548) 2020-04-06 09:24:23 -07:00
version4.go remove EachMode from resource state 2020-04-30 09:22:14 -04:00
write.go always write the current state terraform_version 2019-05-21 18:55:53 -04:00