You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Martin Atkins f0de9b60c1 backend/local: Periodically persist intermediate state snapshots ... Terraform Core emits a hook event every time it writes a change into the in-memory state. Previously the local backend would just copy that into the transient storage of the state manager, but for most state storage implementations that doesn't really do anything useful because it just makes another copy of the state in memory. We originally added this hook mechanism with the intent of making Terraform _persist_ the state each time, but we backed that out after finding that it was a bit too aggressive and was making the state snapshot history much harder to use in storage systems that can preserve historical snapshots. However, sometimes Terraform gets killed mid-apply for whatever reason and in our previous implementation that meant always losing that transient state, forcing the user to edit the state manually (or use "import") to recover a useful state. In an attempt at finding a sweet spot between these extremes, here we change the rule so that if an apply runs for longer than 20 seconds then we'll try to persist the state to the backend in an update that arrives at least 20 seconds after the first update, and then again for each additional 20 second period as long as Terraform keeps announcing new state snapshots. This also introduces a special interruption mode where if the apply phase gets interrupted by SIGINT (or equivalent) then the local backend will try to persist the state immediately in anticipation of a possibly-imminent SIGKILL, and will then immediately persist any subsequent state update that arrives until the apply phase is complete. After interruption Terraform will not start any new operations and will instead just let any already-running operations run to completion, and so this will persist the state once per resource instance that is able to complete before being killed. This does mean that now long-running applies will generate intermediate state snapshots where they wouldn't before, but there should still be considerably fewer snapshots than were created when we were persisting for each individual state change. We can adjust the 20 second interval in future commits if we find that this spot isn't as sweet as first assumed.		3 years ago
..
init	remove deprecated backends (#31711)	4 years ago
local	backend/local: Periodically persist intermediate state snapshots	3 years ago
remote	Backport support for generic hostname to backend/remote	3 years ago
remote-state	Support assume role for cos backend (#32631)	3 years ago
backend.go	remove -always-out	3 years ago
backend_test.go	…
cli.go	Move terraform/ to internal/terraform/	5 years ago
operation_type.go	…
operationtype_string.go	…
testing.go	Use safe or force workspace delete for cloud backend	3 years ago
unparsed_value.go	core and backend: remove redundant handling of default variable values	4 years ago
unparsed_value_test.go	core and backend: remove redundant handling of default variable values	4 years ago