updated cluster doc and examples for the new IOPS change (#446)

* updated cluster doc for the new IOPS change and removed the IOPS config from examples so that they are launched with the default configuration of 3000 IOPS

* update the changes requested

Co-authored-by: Nikhil Singh <[email protected]>

Author: nikhil-mongo

examples/Atlas_Database_Users/atlas_cluster.tf

@@ -17,8 +17,6 @@ resource "mongodbatlas_cluster" "cluster" {
   auto_scaling_disk_gb_enabled = true
   provider_name                = "AWS"
   disk_size_gb                 = 10
-  provider_disk_iops           = 100
-  provider_volume_type         = "STANDARD"
   provider_instance_size_name  = "M10"
   provider_encrypt_ebs_volume  = true
 }

examples/Atlas_Database_Users/versions.tf

@@ -1,7 +1,7 @@
 terraform {
   required_providers {
     mongodbatlas = {
-      source = "terraform-providers/mongodbatlas"
+      source = "mongodb/mongodbatlas"
     }
   }
   required_version = ">= 0.13"

examples/aws-atlas-privatelink/atlas-cluster.tf

@@ -17,8 +17,6 @@ resource "mongodbatlas_cluster" "cluster-atlas" {
   //Provider settings
   provider_name               = "AWS"
   disk_size_gb                = 10
-  provider_disk_iops          = 100
-  provider_volume_type        = "STANDARD"
   provider_encrypt_ebs_volume = true
   provider_instance_size_name = "M10"
 }

examples/aws-atlas-privatelink/versions.tf

@@ -4,7 +4,7 @@ terraform {
       source = "hashicorp/aws"
     }
     mongodbatlas = {
-      source = "terraform-providers/mongodbatlas"
+      source = "mongodb/mongodbatlas"
     }
   }
   required_version = ">= 0.13"

examples/starter/atlas_cluster.tf

@@ -17,8 +17,6 @@ resource "mongodbatlas_cluster" "cluster" {
   auto_scaling_disk_gb_enabled = true
   provider_name                = "AWS"
   disk_size_gb                 = 10
-  provider_disk_iops           = 100
-  provider_volume_type         = "STANDARD"
   provider_instance_size_name  = "M10"
   provider_encrypt_ebs_volume  = true
 }

examples/starter/versions.tf

@@ -1,7 +1,7 @@
 terraform {
   required_providers {
     mongodbatlas = {
-      source = "terraform-providers/mongodbatlas"
+      source = "mongodb/mongodbatlas"
     }
   }
   required_version = ">= 0.13"

website/docs/r/cluster.html.markdown

@@ -298,6 +298,7 @@ But in order to explicitly change `provider_instance_size_name` comment the `lif
     - AZURE - Microsoft Azure
 
 * `provider_disk_iops` - (Optional - AWS Only) The maximum input/output operations per second (IOPS) the system can perform. The possible values depend on the selected `provider_instance_size_name` and `disk_size_gb`.  This setting requires that `provider_instance_size_name` to be M30 or greater and cannot be used with clusters with local NVMe SSDs.  The default value for `provider_disk_iops` is the same as the cluster tier's Standard IOPS value, as viewable in the Atlas console.  It is used in cases where a higher number of IOPS is needed and possible.  If a value is submitted that is lower or equal to the default IOPS value for the cluster tier Atlas ignores the requested value and uses the default.  More details available under the providerSettings.diskIOPS parameter: [MongoDB API Clusters](https://docs.atlas.mongodb.com/reference/api/clusters-create-one/)
+  * You do not need to configure IOPS for a STANDARD disk configuration but only for a PROVISIONED configuration.
 
 * `provider_disk_type_name` - (Optional - Azure Only) Azure disk type of the server’s root volume. If omitted, Atlas uses the default disk type for the selected providerSettings.instanceSizeName.  Example disk types and associated storage sizes: P4 - 32GB, P6 - 64GB, P10 - 128GB, P15 - 256GB, P20 - 512GB, P30 - 1024GB, P40 - 2048GB, P50 - 4095GB.  More information and the most update to date disk types/storage sizes can be located at https://docs.atlas.mongodb.com/reference/api/clusters-create-one/.
 * `provider_encrypt_ebs_volume` - **(Deprecated) The Flag is always true.** Flag that indicates whether the Amazon EBS encryption feature encrypts the host's root volume for both data at rest within the volume and for data moving between the volume and the cluster. Note: This setting is always enabled for clusters with local NVMe SSDs. **Atlas encrypts all cluster storage and snapshot volumes, securing all cluster data on disk: a concept known as encryption at rest, by default.**.