terraform/state/remote
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
..
artifactory.go
artifactory_test.go
azure.go provider/azurerm: Upgrading to AutoRest v8 (#15006) 2017-06-02 15:30:41 +01:00
azure_test.go provider/azurerm: Upgrading to v10 of the Azure SDK (#14004) 2017-06-01 10:18:22 +01:00
etcd.go
etcd_test.go
file.go
file_test.go
gcs.go
gcs_test.go
http.go Basic authentication for HTTP remote state backend 2017-01-19 21:01:50 -05:00
http_test.go
manta.go state/remote: New provider - manta 2016-09-14 20:44:52 +01:00
manta_test.go state/remote: New provider - manta 2016-09-14 20:44:52 +01:00
remote.go remote/swift: Migrate Swift remote state to a backend 2017-06-13 22:04:01 +01:00
remote_test.go Make remote state test run 2017-02-15 14:41:55 -05:00
state.go fix strict remote.State lineage check 2017-08-01 19:34:22 -04:00
state_test.go add mutexes to remote.State 2017-05-25 11:20:52 -04:00
testing.go Have consul state reutrn the lock ID 2017-02-15 14:44:43 -05:00