What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

When deploying a cluster using terraform with storage autoscaling enabled, there is no control over the instance size. Changing the current size (for example M30->M40) is shown in the plan, and apply, then nothing happens to the cluster.

I have an opened support ticket about this here: https://support.mongodb.com/case/01592320

What would you like to see happen?

Describe the desired outcome or enhancement.

Decoupling the storage autoscaling from compute size when use_effective_fields =true when not using compute autoscaling. those two should have no coupling whatsoever, since storage and compute are managed separately - especially when storage autoscaling is allowed to be enabled and compute autoscaling is disabled in the same time.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

My development teams push terraform changes showing their clusters are going to be scaled up (it's showing in the plan+apply outputs) but then nothing happens - this creates confusion and frustration when trying to scale clusters.

What steps, if any, are you taking today to manage this problem?

I might use ignore_changes but it's really a patch and not the recommended approach in terraform.