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
{{ message }}
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.
When trying to add or remove a server entry, terraform wants to replace the existing cluster with a new one with the new configurations. Isn't it better if the cluster just updates?
Terraform will perform the following actions:
# example-cluster must be replaced
-/+ resource "couchbasecapella_hosted_cluster" "adtr-cluster" {
~ id = "redacted" -> (known after apply)
name = "redacted"
# (1 unchanged attribute hidden)
+ servers { # forces replacement
+ compute = "m5.xlarge"
+ services = [
+ "query",
]
+ size = 3
+ storage {
+ iops = 3000
+ storage_size = 100
+ storage_type = "GP3"
}
}
# (4 unchanged blocks hidden)
}
Plan: 1 to add, 0 to change, 1 to destroy.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When trying to add or remove a server entry, terraform wants to replace the existing cluster with a new one with the new configurations. Isn't it better if the cluster just updates?
The text was updated successfully, but these errors were encountered: