Skip to content

Auto scaling of storage cannot be disabled for mongodbatlas_advanced_cluster via "disk_gb_enabled" #677

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BlacCello opened this issue Feb 15, 2022 · 3 comments
Assignees

Comments

@BlacCello
Copy link

Terraform CLI and Terraform MongoDB Atlas Provider Version

Terraform v1.1.5
on linux_amd64
...
+ provider registry.terraform.io/mongodb/mongodbatlas v1.2.0
...

Steps to Reproduce

Create a cluster with the following settings

resource "mongodbatlas_advanced_cluster" "cluster" {
  project_id = var.project_id
  name       = var.cluster_name
  cluster_type           = "REPLICASET"

  replication_specs {
    region_configs {
      electable_specs {
        instance_size = "M10"
        node_count    = 3
      }
      auto_scaling {
        disk_gb_enabled = false
      }
      provider_name = "AZURE"
      priority      = 7
      region_name   = "EUROPE_WEST"
    }
  }
}

The plan shows that the replication_specs object is recreated with disk_gb_enabled = false
Run terraform apply

Expected Behavior

After the apply, storage auto scaling is disabled and subsequent plans don't show any changes

Actual Behavior

Storage auto scaling is enabled when looking at the UI (Cluster Configuration). Subsequent plan/apply runs still want to recreate replication_specs because of storage_autoscaling_enabled -> false but it stays enabled.

Debug Output

Not yet possible for me to create, since the migration to advanced cluster is currently on hold in our project. Nevertheless, I hope that this case is easy enough to reproduce very fast; otherwise I can try to do this the next days.

@nikhil-mongo nikhil-mongo self-assigned this Feb 17, 2022
@nikhil-mongo
Copy link
Collaborator

@BlacCello As per the repro, this seems to be underlying API issue and not related to Terraform provider. I have filed an internal ticket to address this. It is better we can close this here as this will be handled for the API releases and not with Terraform provider.

Thanks

@nikhil-mongo
Copy link
Collaborator

HELP-31579 filed internally.

@themantissa
Copy link
Collaborator

Closing as not a Terraform issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants