doc: DOCSP-60149 -- [TF] Gen2 Atlas M30+ Dedicated Clusters on GCP

[xargom]

Description

Documents Gen2 Atlas M30+ Dedicated Clusters on GCP for mongodbatlas_advanced_cluster (resource and both data sources), aligning with the in-progress cloud-docs update in DOCSP-63232 (integration PR: docs-mongodb-internal#23034). Also includes two small pre-existing clarity fixes surfaced while editing the same sections.

Changes:

• docs/resources/advanced_cluster.md: adds GCP Gen2 support to instance_size, disk_iops, and ebs_volume_type across electable_specs, analytics_specs, and read_only_specs; adds a GCP Gen2 regions link to region_name; reworks the replication_specs independent-disk_iops list into bullets; adds explicit Gen1/Gen2 labeling to the AWS PROVISIONED and Azure disk_iops paragraphs and the HIGH_PERFORMANCE bullet, for symmetry with the new GCP text.
• docs/data-sources/advanced_cluster.md, docs/data-sources/advanced_clusters.md: generalizes disk_throughput and ebs_volume_type descriptions to cover GCP.
• internal/service/advancedcluster/schema.go: mirrors the above into descDiskIops, descDiskThroughput, descEbsVolumeType, and descInstanceSize (MarkdownDescription strings only — no schema/validation changes).
• Updates the 4 links to the upstream manage-clusters Gen2 section anchor, which is being renamed from #aws-gen2-dedicated-clusters to #gen2-dedicated-clusters as part of DOCSP-63232.
• Clarifies an ambiguous "this list" reference in the replication_specs field description (unrelated pre-existing issue, bundled here).

Link to any related issue(s): DOCSP-60149

Note: GCP Gen2 clusters are not yet generally available (ATLAS_GCP_GEN2_CLUSTERS is flag-off). This documents the feature ahead of GA in coordination with the DOCSP-63232 cloud-docs PR (docs-mongodb-internal#23034); merge timing should be coordinated with that release.

Type of change:

• Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
• New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR. A migration guide must be created or updated if the new feature will go in a major version.
• Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
• This change requires a documentation update
• Documentation fix/enhancement

Required Checklist:

• I have signed the MongoDB CLA
• I have read the contributing guides
• I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
• I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
• I have added any necessary documentation (if appropriate)
• I have run make fix and verified my code
• If changes include deprecations or removals I have added appropriate changelog entries.
• If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments

No code or schema behavior changes — MarkdownDescription strings only. go build ./... and go vet ./internal/service/advancedcluster/ pass.

[github-actions]

APIx bot: a message has been sent to Docs Slack channel

[augmentcode]

🤖 Augment PR Summary

Summary: Documents upcoming GCP Gen2 support for M30+ Dedicated Clusters in the Advanced Cluster resource and data sources.
Changes:

• Describes GCP Gen2 tiers, supported regions, Hyperdisk Balanced IOPS limits, and derived throughput.
• Extends storage-field guidance across electable, analytics, and read-only specs.
• Updates generated schema Markdown descriptions to mirror the resource documentation.
• Renames Atlas documentation anchors and clarifies independent per-shard IOPS support.

Technical notes: This is documentation-only; the underlying schema and validation behavior are unchanged.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[Copilot]

Pull request overview

Documents Gen2 Atlas M30+ dedicated cluster behavior on GCP for mongodbatlas_advanced_cluster (resource + both data sources) and aligns upstream Gen2 documentation links, while mirroring the same clarifications into the provider’s MarkdownDescription strings.

Changes:

• Expands instance_size, disk_iops, and ebs_volume_type documentation to include GCP Gen2 (Hyperdisk Balanced) across electable_specs, analytics_specs, and read_only_specs.
• Updates disk_throughput / ebs_volume_type descriptions in the advanced_cluster(s) data sources to cover GCP Gen2 behavior and non-configurability.
• Renames upstream Gen2 docs links to the new #gen2-dedicated-clusters anchor and improves readability of the replication_specs independent-IOPS explanation.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
internal/service/advancedcluster/schema.go	Updates MarkdownDescription strings to match new Gen2/GCP guidance (no schema/behavior changes).
docs/resources/advanced_cluster.md	Adds GCP Gen2 coverage to spec fields, updates upstream Gen2 anchors, and clarifies independent disk_iops support.
docs/data-sources/advanced_clusters.md	Generalizes disk_throughput / ebs_volume_type descriptions to cover GCP Gen2.
docs/data-sources/advanced_cluster.md	Generalizes disk_throughput / ebs_volume_type descriptions to cover GCP Gen2.

Suppressed comments (3)

docs/resources/advanced_cluster.md:838

• Same formatting issue as above: "For AWS, valid configurations are:" is appended to the disk_iops bullet line. For consistency with electable_specs, put it on its own indented line.

* `disk_iops` - (Optional) Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware. You can set this attribute if you selected AWS, GCP, or Azure as your cloud service provider. For AWS, valid configurations are:
  

docs/resources/advanced_cluster.md:821

• This bullet uses "Gen 2" while the rest of this doc uses "Gen2". Using a single form improves consistency and avoids confusion.

* `ebs_volume_type` - (Optional) Type of storage you want to attach to your AWS-provisioned cluster. Set only if you selected AWS as your cloud service provider. You can't set this parameter for a multi-cloud cluster. Don't set this parameter for GCP or Azure clusters. Valid values are:
  * `STANDARD` volume types use gp3 storage. For Gen 2 instance sizes, you can configure IOPS independently of storage size using `disk_iops`.

docs/resources/advanced_cluster.md:849

• This bullet uses "Gen 2" while the rest of this doc uses "Gen2". Using a single form improves consistency and avoids confusion.

* `ebs_volume_type` - (Optional) Type of storage you want to attach to your AWS-provisioned cluster. Set only if you selected AWS as your cloud service provider. You can't set this parameter for a multi-cloud cluster. Don't set this parameter for GCP or Azure clusters. Valid values are:
  * `STANDARD` volume types use gp3 storage. For Gen 2 instance sizes, you can configure IOPS independently of storage size using `disk_iops`.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[QuiqueSanMongo]

lgtm