Vcd_independent_disk increasing size_in_mb forces replacement of disk

Just increased the size of an independent disk for the first time and terraform plan says it will force replacement of all the changed disks. Which is unacceptable in this case, is there a way to work around this in the vcd provider?

  # module.vcd_vapp_module.module.worker[0].vcd_independent_disk.ceph_raw_disk must be replaced
-/+ resource "vcd_independent_disk" "ceph_raw_disk" {
      + datastore_name  = (known after apply)
      ~ id              = "urn:vcloud:disk:a991ac81-5249-46c3-b8cd-1a3ec871d207" -> (known after apply)
      ~ iops            = 0 -> (known after apply)
      ~ is_attached     = true -> (known after apply)
        name            = "zorgo-testing-worker-0-ceph"
      ~ owner_name      = "stemid" -> (known after apply)
      ~ size_in_mb      = 286102 -> 327680 # forces replacement
        # (3 unchanged attributes hidden)
    }

  # module.vcd_vapp_module.module.worker[1].vcd_independent_disk.ceph_raw_disk must be replaced
-/+ resource "vcd_independent_disk" "ceph_raw_disk" {
      + datastore_name  = (known after apply)
      ~ id              = "urn:vcloud:disk:43714779-4e32-4236-b57c-4dfec44df676" -> (known after apply)
      ~ iops            = 0 -> (known after apply)
      ~ is_attached     = true -> (known after apply)
        name            = "zorgo-testing-worker-1-ceph"
      ~ owner_name      = "stemid" -> (known after apply)
      ~ size_in_mb      = 286102 -> 327680 # forces replacement
        # (3 unchanged attributes hidden)
    }