Setting fips_enabled to true on azurerm_kubernetes_cluster in default_node_pool on an existing cluster forces replacement

[MikeKlebolt]

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 and review the contribution guide to help.

Terraform Version

1.2.1

AzureRM Provider Version

3.76

Affected Resource(s)/Data Source(s)

azurerm_kubernetes_cluster

Terraform Configuration Files

# Deploy cluster with `fips_enabled = false`
resource "azurerm_kubernetes_cluster" "aks" {
  default_node_pool {
    fips_enabled = false
    temporary_name_for_rotation = format("%stmp", var.agent_pool_default_name)
  }
}

# Then try changing it to true.
resource "azurerm_kubernetes_cluster" "aks" {
  default_node_pool {
    fips_enabled = true
    temporary_name_for_rotation = format("%stmp", var.agent_pool_default_name)
  }
}

Debug Output/Panic Output

2023-10-18 18:05:06.264784:   # module.prod-aks.module.aks.azurerm_kubernetes_cluster.aks must be replaced
2023-10-18 18:05:06.357509: -/+ resource "azurerm_kubernetes_cluster" "aks" {
2023-10-18 18:05:09.866086:       ~ default_node_pool {
2023-10-18 18:05:10.147955:           ~ fips_enabled                 = false -> true # forces replacement

Expected Behaviour

Terraform leverages temporary_name_for_rotation to perform change.

Actual Behaviour

module.prod-aks.module.aks.azurerm_kubernetes_cluster.aks must be replaced

Steps to Reproduce

No response

Important Factoids

No response

References

#23612

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.