Increasing the ebs volume size of core node destroys the cluster

[karannnn-exe]

Found a bug? Maybe our Slack Community can help.

issue

Increasing the ebs volume size of core node destroys the cluster

Expected Behavior

it should increase the ebs core node size

Screenshots

core_instance_group { ~ id = "ig-1T8BFAAXJM2XC" -> (known after apply) name = "c6-emr-dev-uw2-core"

(2 unchanged attributes hidden)

      - ebs_config { # forces replacement
          - iops                 = 0 -> null
          - size                 = 10 -> null
          - type                 = "gp2" -> null
          - volumes_per_instance = 1 -> null
        }
      + ebs_config { # forces replacement
          + size                 = 20
          + type                 = "gp2"
          + volumes_per_instance = 1
        }
    }

Environment (please complete the following information):

Terraform v1.0.10 on linux_amd64

• provider registry.terraform.io/hashicorp/aws v3.73.0

[karannnn-exe]

@Andriy Knysh @Igor Rodionov @Erik Osterman

[aknysh]

@karannnn-exe

In https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/emr_instance_group#ebs_config

it says

Changing this forces a new resource to be created

I suppose that aws_emr_instance_group gets recreated as described. Does it also recreate the cluster?

In any case, this is the behavior that this module can't control.

[karannnn-exe]

yes, @aknysh I read that.