Closed kshilovskiy closed 7 months ago
Hi @kshilovskiy, thanks for raising this issue. We are workinng on solving this issue by including state property in the kusto cluster. I will link the PR to this issue later.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Terraform Version
1.5.7
AzureRM Provider Version
3.89.0
Affected Resource(s)/Data Source(s)
azurerm_kusto_database
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
state
property of thevirtualNetworkConfiguration
is not changed whenvirtual_network_configuration
block is present in theignore_changes
block.Actual Behaviour
state
property of thevirtualNetworkConfiguration
is not present in the state. So, when the state is applied, even ifvirtual_network_configuration
block is present in theignore_changes
, the cluster is restored to the enabled virtual network configuration state. Therefore there is no way to disable virtualNetworkConfiguration without re-creating the cluster.Steps to Reproduce
terraform apply
Migrate
button in Azure Portal. This will change thevirtualNetworkConfiguration.state
toDisabled
virtual_network_configuration
block to theignore_changes
lifecycle blockterraform apply
Important Factoids
No response
References
No response