Provider version conflict

Terraform
3

Hi Martin@apparentlymart,

Thanks for the help on this!!
With latest terraform and provider versions i did a “state pull” and for the the “google_compute_address” resource the schema version was “1”. Except for that all the others resources were on “0” version as you mentioned.

I did a “terraform state rm” of that resource and again added to state using “terraform import” then it changed backed to schema version of “0”. Now I can do an plan for my changes.

What I want to know is:

  1. Why was this caused in the first place, so that we don’t repeat the mistake?
  2. The fix what I did, is it the correct way to handle this kind of errors?

Thanks

1 Like