Azure / Azure/bicep-registry-modules

[AVM Module Issue]: Issue with Redis Cache Creation

Open
#4,291 9 comments 0 reactions 1 assignee Claimed by @TomazMlakar View on GitHub
Class: Resource Module :package: Needs: Author Feedback :ear: Needs: Immediate Attention :bangbang: Needs: Triage :mag: Status: No Recent Activity :zzz: Status: Response Overdue :triangular_flag_on_post: Type: AVM :a: :v: :m:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

I'm not sure

### Module Name

avm/res/cache/redis

### (Optional) Module Version

0.8.0

### Description

I am creating the Redis Cache using the version 0.8.0 like attached file. When i run the bicep for the first time i get the redis cache created successfully.

As it is supposed to be idempotent and when i run the bicep it is supposed to be the same because nothing is changed, but i get the below error.

I have attached the redis bicep file. Appreciate your help on this.

[redis.txt](https://github.com/user-attachments/files/18547059/redis.txt)

```
"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/4f4c97bc-5a23-49dc-8428-5298ad916fdb/resourceGroups/AZ-US-SC-QA_AMS_DataStores-RG01/providers/Microsoft.Resources/deployments/7r7qc7fbsdbqi-redis","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"BadRequest","message":"The following updates can't be processed in one single request, please send separate request to update them:
```

### (Optional) Correlation Id

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.