terraform/backend
Kaveh Mousavi Zamani 7507e3cd21 backend/gcs: fix locking issue when used with terraform_remote_state
Previously there was a problem with double-locking when using the GCS backend with the terraform_remote_state data source.

Here we adjust the locking methodology to avoid that problem.
2017-12-06 09:36:16 -08:00
..
atlas backend/atlas: accept ATLAS_ADDRESS env var for address 2017-03-16 23:04:07 -07:00
init Migrate Manta Remote state to be a backend 2017-10-30 18:36:50 +02:00
legacy Make backcend/legacy match new Backend iface 2017-02-28 16:35:45 -05:00
local watch for cancellation in plan and refresh 2017-12-05 10:17:20 -05:00
remote-state backend/gcs: fix locking issue when used with terraform_remote_state 2017-12-06 09:36:16 -08:00
backend.go command: also print plan for destroy 2017-06-27 11:22:31 -07:00
cli.go cli: allow disabling "next steps" message in terraform plan 2017-09-14 10:51:41 -07:00
nil.go Update Backend interface to latest iteration 2017-02-28 16:07:07 -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 Fix stringer comments (#15069) 2017-06-05 10:17:35 +01:00
testing.go Obtaining the current metadata before setting it 2017-09-06 12:41:05 -07:00