Terraform State Snapshot Locked to 0.12.13 After Apply
I upgraded my terraform CLI from 0.12.9 to 0.12.13 while attempting to fix a problem unrelated to this bug report. In the process of dubugging this problem, I ran `terraform apply` unsuspecting that it would seemingly (for all intents and purposes) break my state in 0.12.9 forever. It turns out my problem was not solved by upgrading my CLI to 0.12.13 so I downgraded it back to 0.12.9. However, now in my Terraform project and all projects that pull in its state remotely I am experiencing this error on `plan` and `apply`. ``` Error: state snapshot was created by Terraform v0.12.13, which is newer than current v0.12.9; upgrade to Terraform v0.12.13 or greater to work with this state ``` ### Terraform Configuration Files ``` ... terraform { backend "s3" { bucket = "my-bucket" region = "us-west-2" key = "eks-terraform/state" dynamodb_table = "my-dynamodb-table" encrypt = true } } ... ``` ### Expected Behavior After upgrading to 0.12.13, on running `terraform apply` a prominent message is displayed warning me that continuing will upgrade my state and that it will be unusable in older versions of Terraform. Ideally, I would also have to provide some kind of flag or argument to bypass this warning so that I don't accidentally lock my state into this newer release. Alternatively, some kind of mechanism will exist allowing me to revert my state snapshot to a format that's compatible with the older release (0.12.9). ###
Posted by enummela on Nov 5, 2019, 9:00 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
New> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
Terraform State Snapshot Locked to 0.12.13 After Apply
I upgraded my terraform CLI from 0.12.9 to 0.12.13 while attempting to fix a problem unrelated to this bug report. In the process of dubugging this problem, I ran `terraform apply` unsuspecting that it would seemingly (for all intents and purposes) break my state in 0.12.9 forever. It turns out my problem was not solved by upgrading my CLI to 0.12.13 so I downgraded it back to 0.12.9. However, now in my Terraform project and all projects that pull in its state remotely I am experiencing this error on `plan` and `apply`. ``` Error: state snapshot was created by Terraform v0.12.13, which is newer than current v0.12.9; upgrade to Terraform v0.12.13 or greater to work with this state ``` ### Terraform Configuration Files ``` ... terraform { backend "s3" { bucket = "my-bucket" region = "us-west-2" key = "eks-terraform/state" dynamodb_table = "my-dynamodb-table" encrypt = true } } ... ``` ### Expected Behavior After upgrading to 0.12.13, on running `terraform apply` a prominent message is displayed warning me that continuing will upgrade my state and that it will be unusable in older versions of Terraform. Ideally, I would also have to provide some kind of flag or argument to bypass this warning so that I don't accidentally lock my state into this newer release. Alternatively, some kind of mechanism will exist allowing me to revert my state snapshot to a format that's compatible with the older release (0.12.9). ###
Comments (0)
No comments yet. Start the discussion.