Open cosh opened 4 days ago
Hi @cosh, thank you for bringing up this concern. Within the virtual_network_configuration
section, it's not possible for users to adjust the State
, which is why it's omitted from the documentation. As outlined, if a virtual_network_configuration
block is removed from an existing kusto cluster, the State
automatically changes to Disabled
instead of creating a new resource. This approach is designed to prevent unexpected data loss when a virtual_network_configuration
block is deleted.
Some reference code: https://github.com/hashicorp/terraform-provider-azurerm/blob/33649cb3b77e4dd6fed0a43b531ca2d3445f6c2b/internal/services/kusto/kusto_cluster_resource.go#L534-L544 https://github.com/hashicorp/terraform-provider-azurerm/blob/33649cb3b77e4dd6fed0a43b531ca2d3445f6c2b/internal/services/kusto/kusto_cluster_resource.go#L745-L752
Is there an existing issue for this?
Community Note
Terraform Version
1.9.7
AzureRM Provider Version
4.5.0
Affected Resource(s)/Data Source(s)
azurerm_kusto_cluster
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The documentation must be updated with all the config parameters
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
No response