You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
│ Error: updating Server Groupsv 2 (Subscription: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
│ Resource Group Name: "PeterTest10252023"
│ Server Groupsv 2 Name: "peter1025secondary"): performing Update: unexpected status 400 with error: bad_request: Disk size cannot be updated on read replicas.
│
│ with azurerm_cosmosdb_postgresql_cluster.read_replica,
│ on main.tf line 107, in resource "azurerm_cosmosdb_postgresql_cluster""read_replica":
│ 107: resource "azurerm_cosmosdb_postgresql_cluster""read_replica" {
Expected Behaviour
coordinator_storage_quota_in_mb should be optional for azurerm_cosmosdb_postgresql_cluster when it's a read replica.
It seems there are other parameters should be optional for read replica of azurerm_cosmosdb_postgresql_cluster. For example, coordinator_vcore_count. Please check and fix those as well.
Actual Behaviour
╷
│ Error: updating Server Groupsv 2 (Subscription: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
│ Resource Group Name: "PeterTest10252023"
│ Server Groupsv 2 Name: "peter1025secondary"): performing Update: unexpected status 400 with error: bad_request: Disk size cannot be updated on read replicas.
│
│ with azurerm_cosmosdb_postgresql_cluster.read_replica,
│ on main.tf line 107, in resource "azurerm_cosmosdb_postgresql_cluster" "read_replica":
│ 107: resource "azurerm_cosmosdb_postgresql_cluster" "read_replica" {
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
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.
Is there an existing issue for this?
Community Note
Terraform Version
1.5.5
AzureRM Provider Version
3.76.0
Affected Resource(s)/Data Source(s)
azurerm_cosmosdb_postgresql_cluster
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
coordinator_storage_quota_in_mb should be optional for azurerm_cosmosdb_postgresql_cluster when it's a read replica.
I reported similar issue from here:
#23734
It seems there are other parameters should be optional for read replica of azurerm_cosmosdb_postgresql_cluster. For example, coordinator_vcore_count. Please check and fix those as well.
Actual Behaviour
╷
│ Error: updating Server Groupsv 2 (Subscription: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
│ Resource Group Name: "PeterTest10252023"
│ Server Groupsv 2 Name: "peter1025secondary"): performing Update: unexpected status 400 with error: bad_request: Disk size cannot be updated on read replicas.
│
│ with azurerm_cosmosdb_postgresql_cluster.read_replica,
│ on main.tf line 107, in resource "azurerm_cosmosdb_postgresql_cluster" "read_replica":
│ 107: resource "azurerm_cosmosdb_postgresql_cluster" "read_replica" {
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: