If availability_zone_count is 2, terraform thinks it needs to be changed every time for aws_elasticsearch_domain

[tmccombs]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v1.0.9
on linux_amd64
+ provider registry.terraform.io/hashicorp/archive v2.2.0
+ provider registry.terraform.io/hashicorp/aws v3.63.0

Affected Resource(s)

• aws_elasticsearch_domain

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_elasticsearch_domain" "domain" {
  domain_name = "test"
  elasticsearch_version = "6.0"
  
  cluster_config {
    instance_type = "m4.large.elasticsearch"
    instance_count = 2
    zone_awareness_enabled = true
    zone_awareness_config {
      availability_zone_count = 2
   }
   // optional vpc config
 }

Debug Output

Relavent parts, with redacted data: https://gist.github.com/tmccombs/7015a4792aad0be999cb999d9ece5a32

Expected Behavior

After applying changes, the plan shouldn't still say that the availability_zone_count still needs to be changed.

Actual Behavior

Even after updating the availability_zone_count, and verifying in AWS that the zone count is 2, terraform still thinks it needs to be updated.

Steps to Reproduce

1. create an elasticsearch domain with availability_zone_count = 2 and version = 6.0
2. run a plan on that resource

Important Factoids

It looks like AWS doesn't return a ZoneAwarenessConfig section. I'm not sure if it is because the availabililty_zone_count is the default of 2, or if it is because it is an older version of elasticsearch.

References

• Probably related to zone_awareness_enabled is ignored for AWS ES domain resource #15730

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[tmccombs]

I'm pretty sure this is still an issue.