doc: Restructures & updates 2.0 guide (#3616)

Author: maastha

RELEASING.md

@@ -17,11 +17,11 @@ Before triggering a release, view the corresponding [unreleased jira page](https
 
 While QA acceptance tests are run in the release process automatically, we check [workflows/test-suite.yml](https://github.com/mongodb/terraform-provider-mongodbatlas/actions/workflows/test-suite.yml) and see if the latest run of the Test Suite action is successful (it runs every day at midnight UTC time). This can help detect failures before proceeding with the next steps.
 
-### Verify upgrade guide is defined
+### Verify upgrade guide is defined (if required)
 
-**Note**: Only applies if the right most version digit is 0 (considered a major or minor version in [semantic versioning](https://semver.org/)).
+- A document (./docs/guides/X.0.0-upgrade-guide.md) must be provided for each major version, summarizing the most significant features, breaking changes, and other helpful information. For minor version releases, this can be created if there are notable changes that warrant it.
 
-- A doc ./docs/guides/X.Y.0-upgrade-guide.md must be defined containing a summary of the most significant features, breaking changes, and additional information that can be helpful. If not defined the release process will be stopped automatically. The expectation is that this file is created during relevant pull requests (breaking changes, significant features), and not before the release process.
+- The expectation is that this file is created during relevant pull requests (breaking changes, significant features), and not before the release process.
 
 - We keep [Guides](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/master/docs/guides) only for 12 months. Add header `subcategory: "Older Guides"` to previous versions.
 

docs/guides/2.0.0-upgrade-guide.md

@@ -28,32 +28,29 @@ The Terraform MongoDB Atlas Provider version 2.0.0 has the following new feature
 
 ## Breaking Changes
 
-- `mongodbatlas_cloud_backup_schedule`
-  - Resource:
-    - `export` and `auto_export_enabled` are now optional only arguments. This facilitates tracking changes in their configurations. 
+### `mongodbatlas_cloud_backup_schedule`
+Resource:
+  - `export` and `auto_export_enabled` are now optional only arguments. This facilitates tracking changes in their configurations. 
+  - `copy_settings.#.replication_spec_id` attribute has been removed. Use `copy_settings.#.zone_id` instead. To learn more, see the [1.18.0 upgrade guide](../guides/1.18.0-upgrade-guide.md#transition-cloud-backup-schedules-for-clusters-to-use-zones).
 
-- `mongodbatlas_cloud_backup_schedule`
-  - Resource: 
-    - `copy_settings.#.replication_spec_id` attribute has been removed. Use `copy_settings.#.zone_id` instead. To learn more, see the [1.18.0 upgrade guide](../guides/1.18.0-upgrade-guide.md#transition-cloud-backup-schedules-for-clusters-to-use-zones).
+Data source:
+  - `copy_settings.#.replication_spec_id` and `use_zone_id_for_copy_settings` attributes have been removed. Remove any usage of `use_zone_id_for_copy_settings` & replace any references to `copy_settings.#.replication_spec_id` in your configurations with `copy_settings.#.zone_id`. To learn more, see the [1.18.0 upgrade guide](../guides/1.18.0-upgrade-guide.md#transition-cloud-backup-schedules-for-clusters-to-use-zones).
 
-  - Data source:
-    - `copy_settings.#.replication_spec_id` and `use_zone_id_for_copy_settings` attributes have been removed. Remove any usage of `use_zone_id_for_copy_settings` & replace any references to `copy_settings.#.replication_spec_id` in your configurations with `copy_settings.#.zone_id`. To learn more, see the [1.18.0 upgrade guide](../guides/1.18.0-upgrade-guide.md#transition-cloud-backup-schedules-for-clusters-to-use-zones).
 
-
-- `mongodbatlas_maintenance_window`
-  - Resource: 
-    - `hour_of_day` is now required. This clarification prevents errors when creating new resources. 
+### `mongodbatlas_maintenance_window`
+Resource:
+  - `hour_of_day` is now required. This clarification prevents errors when creating new resources. 
 
-- `mongodbatlas_custom_db_role`
-  - Resource: 
-    - `actions` now is set as `TypeSet`. This prevents plan diffs when reordering the `actions` in the resource.  
+### `mongodbatlas_custom_db_role`
+Resource:
+  - `actions` now is set as `TypeSet`. This prevents plan diffs when reordering the `actions` in the resource.  
 
-- `mongodbatlas_global_cluster_config`
-  - Resource: 
-    - `custom_zone_mapping` attribute has been removed. Use `custom_zone_mapping_zone_id` instead. To learn more, see the [Sharding Configuration guide](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/advanced-cluster-new-sharding-schema).
+### `mongodbatlas_global_cluster_config`
+Resource:
+  - `custom_zone_mapping` attribute has been removed. Use `custom_zone_mapping_zone_id` instead. To learn more, see the [Sharding Configuration guide](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/advanced-cluster-new-sharding-schema).
 
-  - Data source:
-    - `custom_zone_mapping` attribute has been removed. Use `custom_zone_mapping_zone_id` instead. To learn more, see the [Sharding Configuration guide](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/advanced-cluster-new-sharding-schema).
+Data source:
+  - `custom_zone_mapping` attribute has been removed. Use `custom_zone_mapping_zone_id` instead. To learn more, see the [Sharding Configuration guide](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/advanced-cluster-new-sharding-schema).
 
 
 

scripts/check-upgrade-guide-exists.sh

@@ -8,8 +8,8 @@ RELEASE_NUMBER=$(echo "${RELEASE_TAG}" | tr -d v)
 
 IFS='.' read -r MAJOR MINOR PATCH <<< "$RELEASE_NUMBER"
 
-# Check if it's a major release (patch version is 0)
-if [ "$PATCH" -eq 0 ]; then
+# Check if it's a major release (minor and patch versions are 0)
+if [ "$PATCH" -eq 0 ] && [ "$MINOR" -eq 0 ]; then
     UPGRADE_GUIDE_PATH="docs/guides/$MAJOR.$MINOR.$PATCH-upgrade-guide.md"
     echo "Checking for the presence of $UPGRADE_GUIDE_PATH"
     if [ ! -f "$UPGRADE_GUIDE_PATH" ]; then