You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# azurerm_linux_web_app.myWebApp will be updated in-place~ resource "azurerm_linux_web_app""myWebApp" {
id = "/subscriptions/<subsId>/resourceGroups/<rgName>/providers/Microsoft.Web/sites/myWebApp"
name = "myWebApp"~ virtual_network_subnet_id = "/subscriptions/<subsId>/resourceGroups/<rgName>/providers/Microsoft.Network/virtualNetworks/<vnetNAme>/subnets/<subVnetName>" ->"subscriptions/<subsId>/resourceGroups/<rgName>/providers/Microsoft.Network/virtualNetworks/<vnetNAme>/subnets/<subVnetName>"
Expected Behaviour
There should not be an update
Actual Behaviour
it seems that because of the "/" in front of the subnet Id the resource "azurerm_linux_web_app.myWebApp" is always updated
Steps to Reproduce
run terraform apply
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
…bnet_id`
This fixes#25832 by ensuring that the Subnet ID is recased
meaning that it'll be in the correct format.
From our side since we're validating the user input for this field, it's hard for us to write a test-case for this one since
it'd be caught by the validation - but this is caused by user input for this field (provisioned through an ARM Template etc)
providing this value without the prefix '/', which the API should be requiring (but isn't).
Is there an existing issue for this?
Community Note
Terraform Version
1.8.2
AzureRM Provider Version
3.101.0
Affected Resource(s)/Data Source(s)
azurerm_linux_web_app
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
There should not be an update
Actual Behaviour
it seems that because of the "/" in front of the subnet Id the resource "azurerm_linux_web_app.myWebApp" is always updated
Steps to Reproduce
run
terraform apply
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: