Sander van Harmelen 394f20f59c backend/remote: do not unlock after a failed upload ... When changes are made and we failed to upload the state, we should not try to unlock the workspace. Leaving the workspace locked is a good indication something went wrong and also prevents other changes from being applied before the newest state is properly uploaded. Additionally we now output the lock ID when a lock or force-unlock action failed.		2019-04-29 21:23:33 +02:00
..
atlas	Change backend.ValidateConfig to PrepareConfig	2019-02-25 18:37:20 -05:00
init	Merge pull request #19070 from mars/postgres-backend	2019-02-26 20:20:01 -05:00
local	backend/local: preserve serial and lineage on failure	2019-03-27 16:15:16 +01:00
remote	backend/remote: do not unlock after a failed upload	2019-04-29 21:23:33 +02:00
remote-state	grammatical updates to comments and docs (#20195)	2019-03-21 14:05:41 -07:00
backend.go	Change backend.ValidateConfig to PrepareConfig	2019-02-25 18:37:20 -05:00
cli.go	backend: Update interface and implementations for new config loader	2018-10-16 18:39:12 -07:00
nil.go	Change backend.ValidateConfig to PrepareConfig	2019-02-25 18:37:20 -05:00
nil_test.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
operation_type.go	backend: introduce the backend set of interfaces	2017-01-26 14:33:49 -08:00
operationtype_string.go	Update various files for new version of "stringer"	2017-12-11 13:26:29 -08:00
testing.go	Change backend.ValidateConfig to PrepareConfig	2019-02-25 18:37:20 -05:00
unparsed_value.go	backend: Cap number of "undeclared variable" warnings at four	2019-03-05 15:42:08 -08:00
unparsed_value_test.go	backend: Cap number of "undeclared variable" warnings at four	2019-03-05 15:42:08 -08:00