mirror of
https://github.com/opentofu/opentofu.git
synced 2024-12-26 00:41:27 -06:00
efdc6e52bc
We've seen some concern about the additional storage usage implied by creating intermediate state snapshots for particularly long apply phases that can arise when managing a large number of resource instances together in a single workspace. This is an initial coarse approach to solving that concern, just restoring the original behavior when running inside Terraform Cloud or Enterprise for now and not creating snapshots at all. This is here as a solution of last resort in case we cannot find a better compromise before the v1.5.0 final release. Hopefully a future commit will implement a more subtle take on this which still gets some of the benefits when running in a Terraform Enterprise environment but in a way that will hopefully be less concerning for Terraform Enterprise administrators. This does not affect any other state storage implementation except the Terraform Cloud integration and the "remote" backend's state storage when running inside a TFC/TFE-driven remote execution environment. |
||
|---|---|---|
| .. | ||
| remote | ||
| statefile | ||
| statemgr | ||
| checks.go | ||
| doc.go | ||
| instance_generation.go | ||
| instance_object_src.go | ||
| instance_object_test.go | ||
| instance_object.go | ||
| module.go | ||
| objectstatus_string.go | ||
| output_value.go | ||
| resource_test.go | ||
| resource.go | ||
| state_deepcopy.go | ||
| state_equal.go | ||
| state_string.go | ||
| state_test.go | ||
| state.go | ||
| sync.go | ||