[3.114.0][azurerm_redis_cache] Changing enable_authentication to authentication_enabled.

[veerasuraj]

Is there an existing issue for this?

• [X] I have searched the existing issues

Community Note

• Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.

Terraform Version

1.3.10

AzureRM Provider Version

3.114.0

Affected Resource(s)/Data Source(s)

azurerm_redis_cache

Terraform Configuration Files

resource "azurerm_redis_cache" "main" {
  name                 = "idpe-${var.cluster_name}"
  location             = var.location
  resource_group_name  = local.resource_group
  capacity             = var.capacity
  family               = "P"
  sku_name             = "Premium"
  non_ssl_port_enabled = true
  minimum_tls_version  = "1.2"
  subnet_id            = azurerm_subnet.main.id
  redis_configuration {
    authentication_enabled = false

  }
}

Debug Output/Panic Output

N/A

Expected Behaviour

With the provider in version v3.114.0, changing enable_authentication to authentication_enabled should remove the depreciation warning as per https://github.com/hashicorp/terraform-provider-azurerm/releases/tag/v3.114.0 and #26608

Actual Behaviour

  ~ redis_configuration {
      ~ enable_authentication                   = false -> true
        # (12 unchanged attributes hidden)
    }
}

Pls note that even after replacing this argument with authentication_enabled., terraform plan is throwing a warning pointing out still to enable_authentication and applying a change in value, even after not doing so.

 Also, we did update the azurerm version to 3.116.0 to test, but the issue remains the same. Hope to get a fix for this at your availability.

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[xuzhang3]

@veerasuraj this change should be fix in v4 and enable_authentication will also be removed in v4

[harshavmb]

This issue looks similar to #26943 & caused by single commit although attributes are different, symptoms are the same.