Mitchell Hashimoto d01886a644 command: remove legacy remote state on migration ...

Fixes #12871

We were forgetting to remove the legacy remote state from the actual
state value when migrating. This only causes an issue when saving a plan
since the plan contains the state itself and causes an error where both
a backend + legacy state exist.

If saved plans aren't used this causes no noticable issue.

Due to buggy upgrades already existing in the wild, I also added code to
clear the remote section if it exists in a standard unchanged backend

2017-03-20 10:14:59 -07:00

..

atlas

backend/atlas: accept ATLAS_ADDRESS env var for address

2017-03-16 23:04:07 -07:00

init

backend/init: add atlas, remove legacy atlas remote state

2017-03-01 13:29:16 -08:00

legacy

Make backcend/legacy match new Backend iface

2017-02-28 16:35:45 -05:00

local

command: remove legacy remote state on migration

2017-03-20 10:14:59 -07:00

remote-state

backend/consul: rebase and modify gzip test

2017-03-14 17:59:54 -07:00

backend.go

command: initial work on migrating envs, basic cases first

2017-03-01 10:59:17 -08: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

backend: introduce the backend set of interfaces

2017-01-26 14:33:49 -08:00

testing.go

Merge pull request #12558 from hashicorp/f-backend-testing

2017-03-15 08:45:20 -07:00