provider[\"registry.terraform.io/elastic/ec\"]" produced an unexpected new value: .elasticsearch.frozen.zone_count: was cty.NumberIntVal(0), but now cty.NumberIntVal(1)

[pomodororosso]

Error during terraform apply upgrading the terraform-provider-ec from 0.5 to 0.10 and having imported the ec_deployment resource into the terraform state file.

When applying changes to ec_deployment.elastic_cloud, provider
"provider[\"registry.terraform.io/elastic/ec\"]" produced an unexpected new
value: .elasticsearch.frozen.zone_count: was cty.NumberIntVal(0), but now
cty.NumberIntVal(1).

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

[irontoby]

Having the same issue with latest provider.

[irontoby]

I think I figured out what's going on here. I'm using a module + variables to set up multiple Elastic Cloud instances. I want to disable warm nodes in the Dev environment so I set warm.node_count to 0 which resulted in the above error.

Instead, if I set size to 0g and node_count to 1 (or, I presume, any positive integer), it has the desired effect of no warm nodes and no error.

This provider would be MUCH easier to parameterize if the hot, warm etc blocks each had an enabled property we could just set to false (both for ec_deployment and elasticstack_elasticsearch_index_lifecycle)