Upgrade to provider v1.44.0 breaks SignalR ID

[oleksiypavlenko]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v0.12.20

• provider.azurerm v1.44.0

Affected Resource(s)

• azurerm_signalr_service

Terraform Configuration Files

resource "azurerm_signalr_service" "mysignalr01" {
  name                = "mysignalr01"
  location            = azurerm_resource_group.resource-group.location
  resource_group_name = azurerm_resource_group.resource-group.name

  sku {
    name     = "Standard_S1"
    capacity = 5
  }

  cors {
    allowed_origins = ["https://somewebsite.com"]
  }

  features {
    flag  = "ServiceMode"
    value = "Default"
  }

  features {
    flag  = "EnableConnectivityLogs"
    value = "True"
  }

  tags = {
    environment = azurerm_resource_group.resource-group.tags.environment
  }
}

Expected Behavior

Terraform should not report any changes after upgrading from AzureRM 1.43.0 provider to AzureRM 1.44.0

Actual Behavior

Error: ID was missing the signalR element

It appears that casing was changed for ID from SignalR to signalR.
See documentation example for import:

terraform import azurerm_signalr_service.example /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/terraform-signalr/providers/Microsoft.SignalRService/SignalR/tfex-signalr

Steps to Reproduce

1. Upgrade AzureRM version from 1.43.0 to 1.44.0
2. Run terraform plan

[ghost]

This has been released in version 2.0.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.0.0"
}
# ... other configuration ...

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!