[Bug]: Changing metro for equinix_metal_vrf should recreate resource #652
Labels
bug
Something isn't working
Comments
cprivitere
added a commit
that referenced
this issue
Oct 3, 2024
While testing a Terraform module that uses the VRF resource, I ran into errors during terraform apply because I changed a metro or project ID variable and Terraform attempted to use my existing VRF rather than deleting it and recreating one in the correct metro or project. This updates the `metal_vrf` resource schema so that Terraform will delete and recreate a VRF if the metro or project ID changes, since those values cannot be updated for a VRF. Fixes #652
|
This issue has been resolved in version 2.7.0 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Terraform Version
Terraform v1.5.7 on darwin_arm64
Equinix Provider Version
version = "1.34.1"
Effected Terraform Resources
equinix_metal_vrf
Terraform Config Files
No response
Debug Output
No response
Panic Output
No response
Expected Behavior
It is not possible to change the metro for an existing VRF in the Metal API: https://deploy.equinix.com/developers/api/metal#tag/VRFs/operation/updateVrf
When the metro attribute is changed for an existing VRF in terraform configuration, the provider should delete the existing VRF and create a new one in the specified metro.
Actual Behavior
When the metro attribute is changed for an existing VRF, the terraform provider throws an error after apply because the value in state does not match the value in config.
Steps to Reproduce
equinix_metal_vrfresourceThe text was updated successfully, but these errors were encountered: