update clu2adv doc

Author: lantoli

README.md

@@ -9,7 +9,7 @@ This repository contains the Atlas CLI plugin for [Terraform's MongoDB Atlas Pro
 The plugin provides the following commands to help with your Terraform configurations:
 
 ### 1. clusterToAdvancedCluster (clu2adv)
-Convert `mongodbatlas_cluster` resources to `mongodbatlas_advanced_cluster` format for Provider 2.0.0.
+Convert `mongodbatlas_cluster` resources to `mongodbatlas_advanced_cluster` Provider 2.0.0 schema.0.0.
 
 **Quick Start:**
 ```bash
@@ -18,10 +18,10 @@ atlas terraform clusterToAdvancedCluster --file in.tf --output out.tf
 atlas tf clu2adv -f in.tf -o out.tf
 ```
 
-[📖 Full Documentation](./docs/command_clu2adv.md) | [Dynamic Blocks Guide](./docs/guide_clu2adv_dynamic_block.md)
+[📖 Full Documentation](./docs/command_clu2adv.md) | [🔄 Migration Guide: Cluster to Advanced Cluster](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/cluster-to-advanced-cluster-migration-guide)
 
 ### 2. advancedClusterToV2 (adv2v2)
-Convert legacy `mongodbatlas_advanced_cluster` configurations to the new Provider 2.0.0 format with simplified structure.
+Convert previous `mongodbatlas_advanced_cluster` configurations to the new Provider 2.0.0 schema with simplified structure.
 
 **Quick Start:**
 ```bash
@@ -51,37 +51,6 @@ If you want to see the list of installed plugins or check if this plugin is inst
 atlas plugin list
 ```
 
-## Provider 2.0.0 Preview
-
-**Note**: To use the **Preview for MongoDB Atlas Provider 2.0.0**, set the environment variable:
-```bash
-export MONGODB_ATLAS_PREVIEW_PROVIDER_V2_ADVANCED_CLUSTER=true
-```
-
-## Quick Migration Guide
-
-### From mongodbatlas_cluster to mongodbatlas_advanced_cluster
-1. Use `clu2adv` to convert your existing cluster configurations
-2. Review the converted output, especially dynamic blocks
-3. Test in a development environment
-4. Apply to production
-
-[Learn more →](./docs/command_clu2adv.md)
-
-### From Legacy to Provider 2.0.0 Format
-1. Use `adv2v2` to update your advanced cluster configurations
-2. Verify the flattened `replication_specs` structure
-3. Check that `region_configs` is now `config`
-4. Test thoroughly before production deployment
-
-[Learn more →](./docs/command_adv2v2.md)
-
-## Examples
-
-Find example conversions in the test data directories:
-- [clu2adv examples](https://github.com/mongodb-labs/atlas-cli-plugin-terraform/tree/main/internal/convert/testdata/clu2adv)
-- [adv2v2 examples](https://github.com/mongodb-labs/atlas-cli-plugin-terraform/tree/main/internal/convert/testdata/adv2v2)
-
 ## Feedback
 
 If you find any issues or have any suggestions, please open an [issue](https://github.com/mongodb-labs/atlas-cli-plugin-terraform/issues) in this repository.
@@ -92,4 +61,4 @@ See our [CONTRIBUTING.md](CONTRIBUTING.md) guide.
 
 ## License
 
-MongoDB Atlas CLI is released under the Apache 2.0 license. See [LICENSE.md](LICENSE.md)
+MongoDB Atlas CLI is released under the Apache 2.0 license. See [LICENSE.md](LICENSE.md)

docs/command_adv2v2.md

@@ -1,6 +1,6 @@
-# Convert mongodbatlas_advanced_cluster to Provider 2.0.0 Format
+# Convert mongodbatlas_advanced_cluster to Provider 2.0.0 schema
 
-This command helps you migrate `mongodbatlas_advanced_cluster` configurations from the legacy SDKv2 format to the new Provider 2.0.0 format.
+ advancedClusterToV2 (adv2v2) command helps you migrate previous `mongodbatlas_advanced_cluster` configurations to the new Provider 2.0.0 schema.
 
 ## Background
 
@@ -12,7 +12,7 @@ MongoDB Atlas Provider 2.0.0 introduces a new, cleaner structure for `mongodbatl
 
 ## Usage
 
-To convert a Terraform configuration from the legacy `mongodbatlas_advanced_cluster` format to the Provider 2.0.0 format, use the following command:
+To convert a Terraform configuration from the previous `mongodbatlas_advanced_cluster` schema to the Provider 2.0.0 schema, use the following command:
 
 ```bash
 atlas terraform advancedClusterToV2 --file in.tf --output out.tf
@@ -25,9 +25,9 @@ atlas tf adv2v2 -f in.tf -o out.tf
 
 ### Command Options
 
-- `--file` or `-f`: Input file path containing the legacy `mongodbatlas_advanced_cluster` configuration
+- `--file` or `-f`: Input file path containing the `mongodbatlas_advanced_cluster` configuration
 - `--output` or `-o`: Output file path for the converted Provider 2.0.0 configuration
-- `--replaceOutput` or `-r`: Overwrite the output file if it exists
+- `--replaceOutput` or `-r`: Overwrite the output file if it exists, or even use the same output file as the input file
 - `--watch` or `-w`: Keep the plugin running and watching for changes in the input file
 
 ## Examples
@@ -454,7 +454,7 @@ replication_specs = concat(
 
 3. **Variable references transformation**: The converter updates variable references (e.g., `replication_specs.value` to `spec`), but complex nested references should be reviewed.
 
-4. **Block ordering**: The Provider 2.0.0 format may handle block ordering differently. Ensure any dependencies on block order are maintained.
+4. **Block ordering**: The Provider 2.0.0 schema may handle block ordering differently. Ensure any dependencies on block order are maintained.
 
 ### General Limitations
 
@@ -476,4 +476,4 @@ If you encounter use cases not yet supported, please send us [feedback](https://
 You can find more examples of dynamic block conversions in the [test data directory](https://github.com/mongodb-labs/atlas-cli-plugin-terraform/tree/main/internal/convert/testdata/adv2v2), particularly:
 - `dynamic_replication_specs.in.tf` / `.out.tf`
 - `dynamic_region_configs.in.tf` / `.out.tf`
-- `dynamic_tags_labels.in.tf` / `.out.tf`
+- `dynamic_tags_labels.in.tf` / `.out.tf`

docs/command_clu2adv.md

@@ -1,13 +1,11 @@
 # Convert mongodbatlas_cluster to mongodbatlas_advanced_cluster
 
-This command helps you migrate from `mongodbatlas_cluster` to `mongodbatlas_advanced_cluster` (preview provider 2.0.0).
+clusterToAdvancedCluster (clu2adv) command helps you migrate from `mongodbatlas_cluster` to `mongodbatlas_advanced_cluster` Provider 2.0.0 schema.
 
 ## Usage
 
 You can find more information in the [Migration Guide: Cluster to Advanced Cluster](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/cluster-to-advanced-cluster-migration-guide).
 
-**Note**: In order to use the **Preview for MongoDB Atlas Provider 2.0.0** of `mongodbatlas_advanced_cluster`, you need to set the environment variable `MONGODB_ATLAS_PREVIEW_PROVIDER_V2_ADVANCED_CLUSTER` to `true`.
-
 If you want to convert a Terraform configuration from `mongodbatlas_cluster` to `mongodbatlas_advanced_cluster`, use the following command:
 ```bash
 atlas terraform clusterToAdvancedCluster --file in.tf --output out.tf
@@ -22,9 +20,9 @@ atlas tf clu2adv -f in.tf -o out.tf
 
 - `--file` or `-f`: Input file path containing the `mongodbatlas_cluster` configuration
 - `--output` or `-o`: Output file path for the converted `mongodbatlas_advanced_cluster` configuration
-- `--includeMoved` or `-m`: Include the `moved blocks` in the output file
 - `--replaceOutput` or `-r`: Overwrite the output file if it exists, or even use the same output file as the input file
 - `--watch` or `-w`: Keep the plugin running and watching for changes in the input file
+- `--includeMoved` or `-m`: Include the `moved blocks` in the output file
 
 ## Examples
 
@@ -55,7 +53,8 @@ dynamic "tags" {
 
 ### Dynamic blocks in regions_config
 
-You can use `dynamic` blocks for `regions_config`. The plugin assumes that `for_each` has an expression which is evaluated to a `list` or `set` of objects. See the [dynamic blocks guide](./guide_clu2adv_dynamic_block.md) to learn more about some limitations.
+You can use `dynamic` blocks for `regions_config`. The plugin assumes that `for_each` has an expression which is evaluated to a `list` of objects.
+
 This is an example of how to use dynamic blocks in `regions_config`:
 ```hcl
 replication_specs {
@@ -75,7 +74,8 @@ replication_specs {
 
 ### Dynamic blocks in replication_specs
 
-You can use `dynamic` blocks for `replication_specs`. The plugin assumes that `for_each` has an expression which is evaluated to a `list` of objects. See the [dynamic blocks guide](./guide_clu2adv_dynamic_block.md) to learn more about some limitations.
+You can use `dynamic` blocks for `replication_specs`. The plugin assumes that `for_each` has an expression which is evaluated to a `list` of objects.
+
 This is an example of how to use dynamic blocks in `replication_specs`:
 ```hcl
 dynamic "replication_specs" {
@@ -102,9 +102,9 @@ If you need to use the plugin for `dynamic` block use cases not yet supported, p
 
 #### Dynamic block and individual blocks in the same resource
 
-Dynamic block and individual blocks for `regions_config` or `replication_specs` are not supported at the same time. The recommended way to handle this is to remove the individual `regions_config` or `replication_specs` blocks and use a local variable to add the individual block information to the variable you're using in the `for_each` expression, using [concat](https://developer.hashicorp.com/terraform/language/functions/concat) if you're using a list or [setunion](https://developer.hashicorp.com/terraform/language/functions/setunion) for sets.
+Dynamic block and individual blocks for `regions_config` or `replication_specs` are not supported at the same time. The recommended way to handle this is to remove the individual `regions_config` or `replication_specs` blocks and use a local `list` variable to add the individual block information to the variable you're using in the `for_each` expression, using [concat](https://developer.hashicorp.com/terraform/language/functions/concat).
 
-Let's see an example with `regions_config`, it is the same for `replication_specs`. In the original configuration file, the `mongodb_cluster` resource is used inside a module that receives the `regions_config` elements in a `list` variable and we want to add an additional `region_config` with a read-only node.
+Let's see an example with `regions_config`, it is the same idea for `replication_specs`. In the original configuration file, the `mongodb_cluster` resource is used inside a module that receives the `regions_config` elements in a `list` variable and we want to add an additional `regions_config` with a read-only node.
 ```hcl
 variable "replication_specs" {
   type = object({