Open gurubanigulati17 opened 2 months ago
Any updates here !?
Any updates here !?
@favoretti Sorry for pinging you directly, but I see you worked on two PRs related to enable AAD (which is mentioned in the error message above) in Redis: https://github.com/hashicorp/terraform-provider-azurerm/pull/23976 and https://github.com/hashicorp/terraform-provider-azurerm/pull/25006 Can you make any sense of the error described by @gurubanigulati17 ? Is this the new expected behaviour?
@thoHeinze I see what is happening, but I don't know why. I'd need to run a couple of tests to try and reproduce it, but I'm unfortunately swamped hard at work right now, it will take me at least 2-3 weeks before I catch a breath to be able to do anything about this, sorry..
Is there an existing issue for this?
Community Note
Terraform Version
0.15.5
AzureRM Provider Version
3.96.0
Affected Resource(s)/Data Source(s)
azurerm_redis_cache
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The operation ought to proceed without the error message indicating, "
The following updates can't be processed in one single request, please send separate request to update them: 'properties.sku.capacity,properties.aadEnableDisable
". In versions 3.82.0 and below, this operation is supported. However, issues arise with versions beyond 3.82.0, wherein the operation fails. In addition, I have conducted tests on all the versions including 3.83.0, 3.84.0, 3.96.0, 3.97.0, 3.98.0, and 3.102.0.Actual Behaviour
We attempted to trigger an update operation which increases the memory from 16 to 32 GB and changes notify_keyspace_events from AK to AKE in one call. However, it resulted in the failure of this update instance operation.
The error message received was '
The following updates can't be processed in one single request, please send separate request to update them: 'properties.sku.capacity,properties.aadEnableDisable
'. This suggests that these changes should be requested separately.Steps to Reproduce
Important Factoids
No response
References
No response