Skip to content
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

instance_size for advance cluster marked as optional in the documentation #1311

Closed
gregoirefra opened this issue Jul 11, 2023 · 3 comments
Closed
Labels

Comments

@gregoirefra
Copy link

Terraform CLI and Terraform MongoDB Atlas Provider Version

Terraform v1.2.6
provider registry.terraform.io/mongodb/mongodbatlas v1.8.1

Terraform Configuration File

resource "mongodbatlas_advanced_cluster" "sandbox" {
  project_id   = var.project_id
  name         = "autoscaling"
  cluster_type = "REPLICASET"
  replication_specs {
    region_configs {
      electable_specs {
        node_count = 3
      }
      auto_scaling {
        disk_gb_enabled           = true
        compute_enabled           = true
        compute_min_instance_size = "M10"
        compute_max_instance_size = "M20"
      }
      provider_name = "AWS"
      priority      = 7
      region_name   = "US_EAST_1"
    }
  }

  provider = mongodbatlas.staging
}

Steps to Reproduce

Expected Behavior

Based on the documentation here the configuration should be valid and not expect an instance size.

Actual Behavior

Received an error message stating a missing required argument.

Terraform has been successfully initialized!
╷
│ Error: Missing required argument
│
│   on sandbox.tf line 7, in resource "mongodbatlas_advanced_cluster" "sandbox":
│    7:       electable_specs {
│
│ The argument "instance_size" is required, but no definition was found.
╵

Additional Context

Based on the code base I believe this is simply a documentation error unless we should be able to not specify the instance size when using auto-scaling.

@github-actions
Copy link
Contributor

Thanks for opening this issue. The ticket INTMDB-926 was created for internal tracking.

@andreaangiolillo
Copy link
Collaborator

Hello 👋
Thanks for opening this issue. The fix will be available in the next release.

Thanks

@andreaangiolillo
Copy link
Collaborator

Hello,
The fix was released in v1.11.0.. Feel free to reopen the issue if you still have the same problem with the latest version.

Thanks

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

No branches or pull requests

2 participants