Hi @displague, would you have a particular usecase of what to do? I checked guides in TF provider docs and there's nothing on this topic. Maybe some text guide from equnix labs site?

@t0mk https://github.com/equinix-labs/terraform-equinix-metal-vrf/blob/main/main.tf would be a similar example. The purpose of this example would be to demonstrate how all of the resources come together to create a logical network that an OS has access to (VLAN + VRF derived IP address is configured in the OS). We don't have to get into what services are run in the OS for the purposes of this.

https://github.com/equinix-labs/terraform-equinix-metal-vrf/tree/main?tab=readme-ov-file#vrf-deployment-on-equinix-platform

Metal-billed interconnection could be used in the example without redundant VCs and VLANs if that helps to simplify what we are demonstrating here. In that case, the VC resource would be generated and managed by the Interconnection service rather than Ansible. The Ansible example could then refer to the VC through an info module as a secondary step (Use X to create this architecture, use Y to access the Metal-billed interconnection immutable VC).

Since Metal-Billed Interconnection deploys Virtual Circuits on its own, this example should be possible with the existing v0.4.0 capabilities.

Any VC improvements to the example could be created in a second example focused on dedicated interconnection.

As I understand it, we need to resolve #61 in order to put a device in L2 mode