terraform-provider-azurerm
terraform-provider-azurerm copied to clipboard
Redis cache data block fails with Invalid address to set
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 "+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.6.0
AzureRM Provider Version
3.93.0
Affected Resource(s)/Data Source(s)
azurerm_redis_cache
Terraform Configuration Files
data "azurerm_redis_cache" "this" {
name = "redis-name"
resource_group_name = "resource-group-name"
}
provider "azurerm" {
features {}
}
Debug Output/Panic Output
data.azurerm_redis_cache.this: Reading...
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: setting `redis_configuration`: Invalid address to set: []string{"redis_configuration", "0", "active_directory_authentication_enabled"}
│
│ with data.azurerm_redis_cache.this,
│ on main.tf line 1, in data "azurerm_redis_cache" "this":
│ 1: data "azurerm_redis_cache" "this" {
│
╵
Expected Behaviour
should not immediately error, and instead successfully pull data for the redis cache. Have tried with multiple redis caches and get this behavior on newest versions of azure provider.
Actual Behaviour
errors immediately with
Error: setting redis_configuration
: Invalid address to set: []string{"redis_configuration", "0", "active_directory_authentication_enabled"}
Steps to Reproduce
terraform plan
Important Factoids
This can be replicated in Azure Commercial and Azure Government
References
N/A
I think this began happening as of 3.83.0, this issue isn't present in 3.82.0
Thank you for taking the time to open this issue. Please subscribe to PR #25094 created by @xuzhang3 for this issue.
How to fix it ? while new version is unreleased
@pasha-top The new version has just been released v3.95.0!
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.