[AVM Module Issue]: Multi-NIC VM's don't have a way to set the primary NIC

[jchancellor-ms]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Bug

(Optional) Module Version

0.10.0

(Optional) Correlation Id

No response

Description

When deploying a virtual machine with multiple network interfaces, there isn't an option to designate which NIC is primary. This is important in certain routing situations where the default route needs to be configured to a particular network.

[jchancellor-ms]

Since we're currently using AzureRM to create NICs, this is a missing capability in the AzureRM provider. We'll look to see if there is an option to do an update on the nic using AzAPI post creation to address this issue.

[jchancellor-ms]

Just making an update here. Looking at an option to have two nic resources where the default or first nic profile is configured on the first and any additional NICs are configured on the second which will have an explicit dependency on the first. This will likely be a breaking change so will try to review with PG first to see if they can do something easier.

[natilik-mikeguy]

Would love to see this as well! As well as the considerations already mentioned, it makes the "overview" page in the portal more friendly by being able to set the primary NIC to the management interface.

The order of network_interface_ids in the azurerm_linux_virtual_machine resource makes the first as a primary. I know lists in Terraform are inherently unordered, but wonder if there is a way using for comprehensions to do it (not had time to test).

[natilik-mikeguy]

Saying that, making the map guys lexicographically sorted does the job for what I need from the looks of it...

network_interfaces = {
"01mgmt" = {...}
"02inside" = {...}
"03outside" = {...}
}