Bumping dedicated cluster cku # forces replacement of cluster

[egor-georgiev]

Recently I've tried to bump number of ckus, as well as network ingress and egress for a cluster (otherwise confluent would reset the latter two parameters and I'll be forced to replace as well), and I got a message that my cluster will get replaced. In Confluent UI, it is possible to upgrade ckus for a dedicated cluster without destruction. Is it possible for the provider to match functionality, or does this one depend on the confluent client?

• TF version: 0.13
• provider version: 0.0.14

13:34:02    # confluentcloud_kafka_cluster.cluster must be replaced
13:34:02  -/+ resource "confluentcloud_kafka_cluster" "cluster" {
13:34:02        ~ bootstrap_servers = "SASL_SSL://pkc-j8d5q.us-east-1.aws.confluent.cloud:9092" -> (known after apply)
13:34:02        ~ cku               = 5 -> 10 # forces replacement
13:34:02        ~ id                = "lkc-abc123" -> (known after apply)
13:34:02          name              = "my-cluster-name"
13:34:02        ~ network_egress    = 750 -> 1500 # forces replacement
13:34:02        ~ network_ingress   = 250 -> 500 # forces replacement
13:34:02          # (6 unchanged attributes hidden)
13:34:02      }