azurerm_redis_cache: error setting patch_schedule/maintenance_window

[etiennetremel]

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.15.4
• AzureRM v2.68.0

Affected Resource(s)

• azurerm_redis_cache

Terraform Configuration Files

data "azurerm_redis_cache" "redis" {
  name                = "my-redis-instance"
  resource_group_name = "my-resource-group"
}

Debug Output

With a simple data block, I'm seeing the following error since the last release of AzureRM, was working fine before:

│ Error: setting `patch_schedule`: Invalid address to set: []string{"patch_schedule", "0", "maintenance_window"}
│
│   with data.azurerm_redis_cache.redis,
│   on main.tf line 12, in data "azurerm_redis_cache" "redis":
│   12: data "azurerm_redis_cache" "redis" {
│

Expected Behaviour

Should no throw an error?

Actual Behaviour

It's not possible to use the redis data resource anymore.

Steps to Reproduce

1. terraform apply

Important Factoids

Could be related to this PR: https://github.com/terraform-providers/terraform-provider-azurerm/pull/12472/files

References

• https://github.com/terraform-providers/terraform-provider-azurerm/pull/12472/files

[github-actions]

This functionality has been released in v2.69.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[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.