data azure_redis_cache returns 404 for patch schedule

[joshvito]

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

Terraform Version

1.1.9

AzureRM Provider Version

3.43.0

Affected Resource(s)/Data Source(s)

azurerm_redis_cache

Terraform Configuration Files

data "azurerm_redis_cache" "this" {
  name                = "redis-dev"
  resource_group_name = "rg-dev"
}

Debug Output/Panic Output

╷
│ Error: obtaining patch schedules for Redi (Subscription: "<GUID>"
│ Resource Group Name: "rg-dev"
│ Redis Name: "redis-dev"): patchschedules.PatchSchedulesClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="There are no patch schedules found for redis cache 'redis-dev'.\r\nRequestID=<GUID>"
│ 
│   with module.redis_connection.data.azurerm_redis_cache.this,
│   on .terraform/modules/redis_connection/main.tf line 60, in data "azurerm_redis_cache" "this":
│   60: data "azurerm_redis_cache" "this" {
│ 
╵

Expected Behaviour

I expect the data.azurerm_redis_cache to be returned without error.
This works in provider version 3.42.0

Actual Behaviour

Plan command throws the 404 error supplied

Steps to Reproduce

Create an azurerm_redis_cache resource with no patch schedule.
Try to access the data.azurerm_redis_cache in another terraform file.
The reported error will throw on Plan command.

Important Factoids

No response

References

not at the time of report

[dave0783]

We too are experiencing this issue.

[jhernandez-vendavo]

I have the same issue. It appears a PR has been submitted to fix it.

[rcskosir]

Thanks for taking the time to submit this issue. It looks like this has been resolved as of #20516 As such, I am going to mark this issue as closed.

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