James Bardin 9e4c0ff2ad call PersistState immediately when cancelling ... When the backend operation is cancelled, immediately call PersistState. The is a high likelihood that the user is going to terminate the process early if the provider doesn't return in a timely manner, so persist as much state as possible.		2017-05-25 11:20:51 -04:00
..
atlas	backend/atlas: accept ATLAS_ADDRESS env var for address	2017-03-16 23:04:07 -07:00
init	convert S3 remote state to a backend	2017-03-22 10:59:37 -04:00
legacy	Make backcend/legacy match new Backend iface	2017-02-28 16:35:45 -05:00
local	call PersistState immediately when cancelling	2017-05-25 11:20:51 -04:00
remote-state	check for named s3 states before acquiring a lock	2017-05-19 14:40:59 -04:00
backend.go	provide contexts to clistate.Lock calls	2017-04-01 17:09:20 -04:00
cli.go	command: use backend.CLIIinit	2017-02-28 10:58:29 -08:00
nil_test.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
nil.go	Update Backend interface to latest iteration	2017-02-28 16:07:07 -05:00
operation_type.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
operationtype_string.go	Restore stringer-generated files back to new version	2017-04-21 14:49:18 -07:00
testing.go	test for proper state persistence	2017-03-23 10:06:07 -04:00