fix: force recreation of VRF if metro or project ID changes #790
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ctreatma
changed the title
ctreatma
changed the title
ocobles
approved these changes
Oct 3, 2024
|
This PR is included in version 2.7.0 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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_vrfresource 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