azurerm_dev_test_virtual_network - attach existing subnet of existing VNet to DevTest Lab

[MaxiPalle]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Currently, only a new VNet and subnet are created using this resource provider. We need to integrate existing subnet.

New or Affected Resource(s)

• azurerm_dev_test_virtual_network

Potential Terraform Configuration

resource "azurerm_dev_test_virtual_network" "vnet-dtl-lab1" {
  vnet_id                = azurerm_virtual_network.vnet-dtl.id
  lab_name            = azurerm_dev_test_lab.lab1.name
  resource_group_name = azurerm_resource_group.dtl-lab1.name

  subnet {
    subnet_id                   = azurerm_subnet.subnet-example.id
    use_public_ip_address           = "Deny"
    use_in_virtual_machine_creation = "Allow"
  }
}

References

• 0000

[MaxiPalle]

Any update on this? We still need this!

[schwarzzz]

It looks like the current modelling of DevTest Lab resources in the azurerm provider prevents proper dependency inversion:

• The azurerm_dev_test_lab resource does not provide some kind of virtual_network_id argument.
• At the same time, the azurerm_dev_test_virtual_network resource requires a lab_name argument.

In real life, you most probably want to create the DevTest Lab instance on an already existing vNet.

[eehret]

I also need this functionality. This issue has been open for a really long time with no apparent movement. Is it not feasible to support this? I find it odd that you can do this via Azure Portal but not via Terraform.