Open scottslowe opened 1 month ago
@scottslowe both warnings should be addressed on Azure/terraform-azurerm-aks side to reflect changes in hashicorp/terraform-provider-azurerm, I don't think we can do anything about it:
https://github.com/Azure/terraform-azurerm-aks/blob/main/main.tf#L305 https://github.com/hashicorp/terraform-provider-azurerm/issues/25756
https://github.com/Azure/terraform-azurerm-aks/blob/main/main.tf#L552 https://github.com/hashicorp/terraform-provider-azurerm/pull/22478
I’ve opened this issue upstream: https://github.com/Azure/terraform-azurerm-aks/issues/578
To anyone who has concern about this issue: no worries about the deprecation message, these arguments would be removed in v4.0
, if we could pinned the azurerm
provider's major version like we have done in Azure/terraform-azurerm-aks module for this module, we'll be ok.
When running
terraform apply
, this module throws some deprecation warnings. The module still appears to work, but the deprecation warnings might be an indicator of changes we should make to prevent future issues.The deprecation warnings are:
These warnings are produced both with Terraform (tested with 1.8.x) and OpenTofu (tested with 1.7.x).