Open jonas-budde opened 1 day ago
Thanks for raising this issue. Seems it's by TF design since the import function will perform an import based on the actual configuration of the resources on Azure.
@neil-yechenwei Yes, and I would expect that the actual configuration of my Azure resources gets compared to my terraform code. If the TF performs an "import based on the actual configuration", then TF should want to change the DNS server on the next apply, or am I wrong? Because in my TF code I didn't specify a DNS server but in the portal a specified one.
Is there an existing issue for this?
Community Note
Terraform Version
Terraform v1.9.6
AzureRM Provider Version
4.10.0
Affected Resource(s)/Data Source(s)
azurerm_virtual_network
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Terraform should check that there is a difference between default (Azure Provided DNS Server) and the imported resources DNS Server (10.0.0.1). On the next apply the default DNS Server should be configured to the default (Azure provided), because I don't have the custom one in my configuration.
Actual Behaviour
On the Debug Output you can see, that terraform knows about the custom dns server i configured (10.0.0.1). After I imported the vnet (with cli or import block) the apply said: "No changes. Your infrastructure matches the configuration."
Steps to Reproduce
No response
Important Factoids
No response
References