Currently when using my own private dns zone and a shared cidr, each module attempts to link the privatendpoint cidr to the existing zone. Since this is handled outside of the module and using the shared cidr, the module will fail saying that the cidr link already exisists.
----[start]----
│ {"error":{"code":"Conflict","message":"Private zone 'privatelink.openai.azure.com' is already linked to the virtual network '\/subscriptions\/FOO\/resourceGroups\/private-endpoint\/providers\/Microsoft.Network\/virtualNetworks\/vnet'."},"status":"Failed"}
│ -----[end]-----
Is there an existing issue for this?
Description
Currently when using my own private dns zone and a shared cidr, each module attempts to link the privatendpoint cidr to the existing zone. Since this is handled outside of the module and using the shared cidr, the module will fail saying that the cidr link already exisists.
Can we make the module for linking a
New or Affected Resource(s)/Data Source(s)
resource "azurerm_private_dns_zone_virtual_network_link" "dns_zone_link"
Potential Terraform Configuration
References
No response