Adding new instances on aws_elasticsearch_domain with ebs_volume does not work if ebs_option has not changed

[hashibot]

This issue was originally opened by @SilverXion as hashicorp/terraform#11004. It was migrated here as part of the provider split. The original body of the issue is below.

---

When applying change for "instance_count" for an instance type using ebs_volume (ex: t2.medium.elasticsearch), if the ebs_options have not changed, the following error is prompt:

aws_elasticsearch_domain.logs: ValidationException: New cluster configuration has insufficient storage capacity for your current data. The new configuration only supports up to 0.0GB

Terraform Version

v0.7.9

Affected Resource(s)

• aws_elasticsearch_domain

Expected Behavior

Even if the ebs_options have not changed, they should be passed down to aws when adding new instances.

Actual Behavior

If the ebs_options do not change, the volume_size passed to the new instance seems to be 0.

Steps to Reproduce

1. terraform apply

Initial Configuration:
cluster_config { instance_type = "t2.medium.elasticsearch" instance_count = "2" zone_awareness_enabled = "true" }
ebs_options { ebs_enabled = "true" volume_type = "standard" volume_size = "35}" }
New Configuration:
cluster_config { instance_type = "t2.medium.elasticsearch" instance_count = "4" zone_awareness_enabled = "true" }
ebs_options { ebs_enabled = "true" volume_type = "standard" volume_size = "35}" }

Addiotional Information

The same command will apply correctly if the ebs_options are changed, ex:
ebs_options { ebs_enabled = "true" volume_type = "standard" volume_size = "34}" }

[dsalbert]

#1131

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!