terraform/command/testdata/backend-new-legacy/local-state-old.tfstate

{
    "version": 4,
    "terraform_version": "0.14.0",
    "serial": 7,
    "lineage": "backend-new-legacy",
    "remote": {
        "type": "local",
        "config": {
            "path": "local-state-old.tfstate"
        }
    }
}
command: convert to use backends 2017-01-19 05:50:45 +01:00			`{`
refactor tests to use modern states.State in favor of terraform.State where possible 2020-09-30 22:07:54 +02:00			`"version": 4,`
			`"terraform_version": "0.14.0",`
command: convert to use backends 2017-01-19 05:50:45 +01:00			`"serial": 7,`
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 18:05:24 +01:00			`"lineage": "backend-new-legacy",`
			`"remote": {`
			`"type": "local",`
			`"config": {`
			`"path": "local-state-old.tfstate"`
			`}`
			`}`
command: convert to use backends 2017-01-19 05:50:45 +01:00			`}`