James Bardin 32ae05c342 fix strict remote.State lineage check ...

We can't check lineage in the remote state instance, because we may need
to overwrite a state with a new lineage. Whil it's tempting to add an
optional interface for this, like OverwriteState(), optional interfaces
are never _really_ optional, and will have to be implemented by any
wrapper types as well.

Another solution may be to add a State.Supersedes field to indicate that
we intend to replace an existing state, but that may not be worth the
extra check either.

2017-08-01 19:34:22 -04:00

..

remote

fix strict remote.State lineage check

2017-08-01 19:34:22 -04:00

testdata

Use NewLockInfo to get a pre-populated value

2017-02-15 14:41:55 -05:00

backup_test.go

add mutexes to Local, Backup, and InmemState

2017-05-25 11:20:52 -04:00

backup.go

add mutexes to Local, Backup, and InmemState

2017-05-25 11:20:52 -04:00

inmem_test.go

test LockWithContext

2017-04-03 11:50:19 -04:00

inmem.go

state: more robust handling of state Serial

2017-07-05 12:34:30 -07: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

fix windows locking

2017-02-17 13:29:48 -05:00

local_test.go

add mutexes to Local, Backup, and InmemState

2017-05-25 11:20:52 -04:00

local.go

state: more robust handling of state Serial

2017-07-05 12:34:30 -07:00

lock_test.go

backend/consul: support "lock" option to disable locking

2017-03-14 17:59:10 -07:00

lock.go

backend/consul: support "lock" option to disable locking

2017-03-14 17:59:10 -07:00

state_test.go

remove Sleep from TestLockWithContext

2017-04-03 14:46:22 -04:00

state.go

state: more robust handling of state Serial

2017-07-05 12:34:30 -07:00

testing.go

update TestState helper

2017-07-05 17:18:12 -04:00