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

..

test-fixtures

Fixup the tests

2019-04-25 10:32:00 +02:00

backend_apply_test.go

backend/remote: check for external updates

2019-03-08 19:18:07 +01:00

backend_apply.go

backend/remote: check for external updates

2019-03-08 19:18:07 +01:00

backend_common.go

use scanner for reading logs

2019-04-25 11:17:08 -07:00

backend_context.go

Prevent a panic caused by writing to a nil map

2019-04-11 14:34:14 +02:00

backend_mock.go

Fixup the tests

2019-04-25 10:32:00 +02:00

backend_plan_test.go

Fixup the tests

2019-04-25 10:32:00 +02:00

backend_plan.go

Fixup the tests

2019-04-25 10:32:00 +02:00

backend_state_test.go

backend/remote: cleanup test connections

2019-02-07 09:55:19 +01:00

backend_state.go

backend/remote: do not unlock after a failed upload

2019-04-29 21:23:33 +02:00

backend_test.go

Change backend.ValidateConfig to PrepareConfig

2019-02-25 18:37:20 -05:00

backend.go

Merge pull request #20615 from hashicorp/svh/f-input-context

2019-03-08 18:44:28 +01:00

cli.go

Change how to fall back from remote to local backend

2018-11-20 22:25:52 +01:00

colorize.go

backend/remote: implement the Local interface

2018-11-26 20:50:25 +01:00

remote_test.go

Change how to fall back from remote to local backend

2018-11-20 22:25:52 +01:00

testing.go

update test for new go-tfe version

2019-04-24 16:46:17 -07:00