Dmitry Onishchenko

I think the considerations from https://github.com/elastic/terraform-provider-ec/issues/466#issuecomment-1236947482 can be applied here as well.

It looks like `lock` argument works only when `version_regex` is set to "latest". If so we need to update the docs.

I think this is a limitation of our implementation. The output variable isn’t reevaluated by Terraform because its value already known (it’s empty string in our case) even despite the...

> Is it expected behavior that `terraform plan/apply` will still list `0g` topologies? I find it confusing as it _implies_ a change to the infrastructure that is not going to...

TL;DR - it's expected. When 'terraform plan` is executed, TF calls the provider `Read` function that gets actual deployment state. Then TF calculates the diff between config and state. The...

I've started working on this but had to switch to more urgent tasks. I'll return to the ticket once these tasks are done.

@pascal-hofmann we’re evaluating needed efforts and prioritising it at the moment.

@pascal-hofmann , would you mind to share a branch with your changes?

The defect indeed is caused by the same logic and limitations that cause #336. The possible workaround: ### If autoscale disabled **Initial deployment creation** Topology elements (tiers) with non-zero sizes...

@kuisathaverat , can you please check why acceptance failed