SignalR shows a bug in the provider from version 3.49 to 3.56 with the http_request_logs_enabled | http_request_logs_enabled was cty.False, but now null

[Joseluismantilla]

Is there an existing issue for this?

• I have searched the existing issues

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 Version

1.4.6

AzureRM Provider Version

3.56.0

Affected Resource(s)/Data Source(s)

azurerm_signalr_service

Terraform Configuration Files

Resource code:

resource "azurerm_signalr_service" "signalr" {
  name                = var.signalr_name
  location            = var.location
  resource_group_name = var.resource_group_name
  tags                = var.tags
  sku {
    name     = var.signalr_sku
    capacity = var.signalr_capacity
  }
}

Module called:

module "signalr" {
  source                        = local_path
  for_each                      = var.signalr
  signalr_name                  = each.value.signalr_name
  resource_group_name           = module.resource_group.name
  location                      = each.value.location
  signalr_sku                   = each.value.signalr_sku
  signalr_capacity              = each.value.signalr_capacity
  tags                          = "location" = each.value.location
  depends_on                    = [module.resource_group]
} 

Variables file:

# SignalR
variable "signalr" {
   type = map(object({
    signalr_name              = string      
    location                  = string
    signalr_sku               = string
    signalr_capacity          = string
  }))
}

Tfvar file:

signalr = {
  signalr01 = {
    signalr_name                      = "signalr01"    
    location                          = "eastus2"
    signalr_sku                       = "Premium_P1"
    signalr_capacity                  = "1"
  }
}

Debug Output/Panic Output

When expanding the plan for module.signalr["signalr01"].azurerm_signalr_service.signalr to include new values learned so far during apply, provider

│ "registry.terraform.io/hashicorp/azurerm" produced an invalid new value for .http_request_logs_enabled: was cty.False, but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Expected Behaviour

The provider version 3.48 works fine but when I tried to use 3.49 to 3.56.0 and after testing one by one, the provider shows the same error, it can't send the false value even after adding the http_request_logs_enabled = false in the resource, so I wasn't able to increase the provider version yet.

Actual Behaviour

I'm using the 3.48 provider version because with higher, SignalR resource fails.

Steps to Reproduce

terraform init -upgrade
terraform apply -auto-approve

Important Factoids

No response

References

No response