James Bardin 0c1b138719 Add state locking during backend init ... During backend initialization, especially during a migration, there is a chance that an existing state could be overwritten. Attempt to get a locks when writing the new state. It would be nice to always have a lock when reading the states, but the recursive structure of the Meta.Backend config functions makes that quite complex.		2017-02-09 15:47:27 -05:00
..
remote	Fix format string and typos	2017-02-09 10:27:42 -05:00
testdata	Add basic local state locking	2017-01-30 17:16:57 -05:00
backup_test.go
backup.go	Don't create empty backups	2017-01-30 17:16:57 -05:00
cache_test.go	Make sure test has a valid ResourceState	2016-11-20 13:13:43 -05:00
cache.go	Add remote state locking	2017-01-30 17:16:57 -05:00
inmem_test.go
inmem.go	state: deep copies are required	2015-02-23 21:36:58 -08:00
local_lock_unix.go	Switch from Path to PathOut on LocalState.written	2017-01-30 17:16:57 -05:00
local_lock_windows.go	add msdn link for LockFileEx	2017-02-01 12:38:10 -05:00
local_test.go	Use single state.LockInfo struct	2017-02-08 11:34:31 -05:00
local.go	Add state locking during backend init	2017-02-09 15:47:27 -05:00
state_test.go	Silence state package logs during tests	2017-01-30 17:16:57 -05:00
state.go	Change lock reason -> info	2017-02-02 18:08:28 -05:00
testing.go	Fix vet issues	2016-10-18 11:11:12 -04:00