Asymmetric hardware is not supported by the provider

[lisenet]

Terraform CLI and Terraform MongoDB Atlas Provider Version

terraform --version
Terraform v1.3.4
on linux_amd64
+ provider registry.terraform.io/gavinbunney/kubectl v1.13.2
+ provider registry.terraform.io/hashicorp/archive v2.2.0
+ provider registry.terraform.io/hashicorp/aws v4.57.1
+ provider registry.terraform.io/hashicorp/cloudinit v2.2.0
+ provider registry.terraform.io/hashicorp/dns v3.2.3
+ provider registry.terraform.io/hashicorp/helm v2.4.1
+ provider registry.terraform.io/hashicorp/http v3.2.1
+ provider registry.terraform.io/hashicorp/kubernetes v2.7.1
+ provider registry.terraform.io/hashicorp/null v3.1.1
+ provider registry.terraform.io/hashicorp/random v3.1.3
+ provider registry.terraform.io/hashicorp/tls v3.3.0
+ provider registry.terraform.io/mongodb/mongodbatlas v1.9.0

Steps to Reproduce

We use a base tier MongoDB cluster (M20) and an analytics tier (M30), where they are of different sizes due to different business requirements. Currently this is failing in Terraform unless tiers use the same hardware (e.g. either both are set to M20 or M30).

Expected Behavior

Different hardware supported.

Actual Behavior

Error: error reading MongoDB Cluster (development): GET https://cloud.mongodb.com/api/atlas/v1.0/groups/1234567890/clusters/development: 400 (request "ASYMMETRIC_HARDWARE_INVALID") Asymmetric hardware is not supported by the v1.0 API. Please use the v1.5 API instead. Documentation for the v1.5 API is available at https://docs.atlas.mongodb.com/reference/api/clusters-advanced/.

[github-actions[bot]]

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

[Zuhairahmed]

hi @lisenet this functionality is supported on mongodbatlas_advanced_cluster resource. can you test and let us know if this resolves this issue?

[lisenet]

Hi @Zuhairahmed, it does indeed, thanks.