-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
How to use computer_instance_migrate? #509
Comments
Once you download the next release (it'll be out today), you should get migrated automatically. I think this happens when you first run |
We actually cloned master and built the provider using go. We then pointed our tf code at our custom built provider and did a plan and nothing got migrated. Is this a bug? |
All it informed us was that the resource was going to blow away our instance and recreate it. |
It looks like we have a bug in this. The good news is it's really easy to mitigate. We'll be releasing a v1.0.1 ASAP to resolve the problem. Sorry for the issues! |
Thanks for the quick update. We will be waiting |
@paddycarver I'm back. Now it's constantly showing a modification in place needs to happen but never actually performs it on the apply. It looks like it's not actually updating the attached_disk.0.source attribute |
Can you post the output of |
@danawillow Are you all on some sort of public chat where i can send this via Private message? |
While I want to be clear this is not an official HashiCorp resource, HashiCorp has no influence there, and there's no guarantee that HashiCorp employees will be logged in there, Dana and I happen to both be in the GCP community Slack in the Terraform channel. |
Yup, Paddy and I are in the GCP slack which you can get an invite for at https://gcp-slack.appspot.com/. I'm danahoffman there and he's paddy. |
It's almost like my invite got lost into oblivion. |
<!-- This change is generated by MagicModules. --> /cc @rileykarson
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
We are trying to convert to the new way of specifying compute instance disks. I noticed that @danawillow merged in a feature to perform a migration. How do we run this migration to ensure our instances do not get destroyed and recreated and the state gets migrated from v3 to v4 correctly?
The text was updated successfully, but these errors were encountered: