Open Fuxbert opened 5 months ago
Not sure whether this is supported today. equinix_metal_virtual_circuit
resource is just for creating new VCs on dedicated ports, but since shared ports autogenerate their VCs they cannot be updated that way. We would need to bypass the VRF configuration in the equinix_metal_connection
as we do with vlans or create a new resource like equinix_metal_virtual_circuit_config
vnid should be create earlier to create virtual-circuit
It's not relevant to what's discussed here, but you should replace that null_resource
with https://registry.terraform.io/providers/hashicorp/time/latest/docs/resources/sleep
v2.1.0 updated the metal_virtual_circuit
resource so that it can be used with shared virtual circuits, so this nni_vlan
error should not occur when using that version of the provider. However, note that for a shared virtual circuit you must specify the virtual_circuit_id
attribute instead of the connection_id
attribute.
Terraform Version
Terraform v1.7.4
Equinix Provider Version
version = "1.33.0"
Effected Terraform Resources
equinix_metal_vrf equinix_metal_connection equinix_metal_virtual_circuit
Terraform Config Files
Debug Output
Panic Output
No response
Expected Behavior
Expectation is that TF provider will use the existing nni_vlan and just add the bgp details as provided in the resource config
Actual Behavior
Provisioning fails, provider requires the nni_vlan. If I provide this using
the provider will ask for the vnid attribute. Again, providing this (with same reference as the nni_vlan), it fails with
Steps to Reproduce
see above