Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

command: fix loading legacy remote state + migration guide #12320

Merged
merged 3 commits into from
Mar 1, 2017

Conversation

mitchellh
Copy link
Contributor

While doing manual run-throughs of upgrade paths (using both an old + new binary and trying various craziness), I found that the way we load legacy remote state actually doesn't work at all.

We were previously loading from the old way to initialize remote state but as we've been migrating them to the new system we've deleted those old ones, so this was resulting in things like "consul remote state type not found."

I've changed it to use the new initialization system. All tests still pass and manual tests are looking good.

While there, I added a comprehensive upgrade guide for backends. This covers explicit steps for backing up and migrating to backends.

@mitchellh mitchellh added this to the Terraform 0.9 milestone Mar 1, 2017
@mitchellh mitchellh requested a review from jbardin March 1, 2017 03:31
@mitchellh mitchellh merged commit 549d525 into master Mar 1, 2017
@mitchellh mitchellh deleted the b-legacy-state branch March 1, 2017 20:39
@ghost
Copy link

ghost commented Apr 16, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants