Guide and minor main page changes for 1.1.0 (#609)

* Guide and minor main page changes for 1.1.0

* spelling error

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/index.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/index.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/index.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

* Improves based on docs review

Clarify the resources are deprecated and that they will be removed later.

* Update website/docs/guides/1.1.0-upgrade-guide.html.markdown

Co-authored-by: John Williams <[email protected]>

Co-authored-by: John Williams <[email protected]>

Author: themantissa

website/docs/guides/1.1.0-upgrade-guide.html.markdown

@@ -8,73 +8,90 @@ MongoDB Atlas Provider 1.1.0: Upgrade and Information Guide
 
 # MongoDB Atlas Provider 1.1.0: Upgrade and Information Guide
 
-The Terraform MongoDB Atlas Provider version 1.0.0 has a number of new and exciting features and changes.
+The Terraform MongoDB Atlas Provider version 1.1.0 has a number of new and exciting features and changes.
 
-* Cloud Backup Snapshot replaces the now deprecated Cloud Provider Snapshot.
-* Cloud Backup Snapshot Restore Job replaces the now deprecated Cloud Provider Snapshot Restore Job.
+New Features:
 
-1.1.0 also includes general improvements and bug fixes. See the [CHANGELOG](https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/CHANGELOG.md) for more specific information.
+* You can now manage multi-cloud deployments with [`mongodbatlas_advanced_clusters`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/advanced_clusters).
+* You can now manage invitations with
+[`mongodbatlas_org_invitation`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/org_invitation) and [`mongodbatlas_project_invitation`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project_invitation).
+* You can now use `project_owner_id` to set a default owner of projects that you create with [`mongodbatlas_project`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project).
+* [`mongodbatlas_privatelink_endpoint`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/privatelink_endpoint) and [`mongodbatlas_privatelink_endpoint_service`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/privatelink_endpoint_service) now support private endpoints on Google Cloud with Private Service Connect.
+* You can now set `with_default_alerts_settings` to `false` to disable the default alerts when you create projects with [`mongodbatlas_project`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project).
+* [`mongodbatlas_search_index`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/search_index) now supports synonyms.
+* You can now create Atlas Serverless deployments (available as a preview feature) with [`mongodbatlas_serverless_instance`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/serverless_instance).
 
-## Migration from Cloud Provider Snapshot to Cloud Backup Snapshot
+Changes:
 
-There are two possible options to upgrade from v1.0.2 to v1.1.0 from the existing resources `mongodbatlas_cloud_provider_snapshot_backup_policy` to the new ones
+Version 1.1.0 deprecates the following resources:
 
+* [`mongodbatlas_cloud_provider_snapshot`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_provider_snapshot)
+* [`mongodbatlas_cloud_provider_snapshot_restore_job`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_provider_snapshot_restore_job)
 
-### Option 1:  Remove the existing and import the new resource
+If your Terraform configuration uses these resources, see [Migration from Cloud Provider Snapshot to Cloud Backup Snapshot](#migration-from-cloud-provider-snapshot-to-cloud-backup-snapshot) to migrate to the new resources **before you upgrade**.  These resources will be removed in a future major version.
 
-1. Remove your existing `mongodbatlas_cloud_provider_snapshot` resources from terraform state
-   **NOTE** before doing any terraform state change please do a backup
+1.1.0 also includes general improvements and bug fixes. See the [CHANGELOG](https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/CHANGELOG.md) for more specific information.
 
-```bash
-$ terraform state rm mongodbatlas_cloud_provider_snapshot.test
-```
+## Migration from Cloud Provider Snapshot to Cloud Backup Snapshot
 
-2. Change the version of provider to the v1.1.0
+The term **Cloud Provider** has been deprecated in favor of the term **Cloud Backup**.  In order to support this change within the Terraform provider, related resources and data sources with the older terminology have been deprecated and new resources and data sources have been added to support the new terminology.  The deprecated resources and data sources will be removed in a future major version.   We recommend migrating to the new resources as soon as possible by selecting a method from one of the following two options:
 
-3. In order to import the new resource, you must first change your Terraform configuration file, replacing `mongodbatlas_cloud_provider_snapshot_backup_policy` with `mongodbatlas_cloud_backup_schedule`. See the example shared above or find more information in the [mongodbatlas_cloud_backup_schedule](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_backup_schedule)
+### Option 1: Replace the name of resource in Terraform state
 
-4. Perform an import of your existing `mongodbatlas_cloud_provider_snapshot` to `mongodbatlas_cloud_backup_snapshot`
-```bash
-    terraform import mongodbatlas_cloud_backup_snapshot.test <project_id>-<cluster_name>-<snapshot_id>
-```
+1. Replace the name of the deprecated resource `mongodbatlas_cloud_provider_snapshot` with the new name `mongodbatlas_cloud_backup_snapshot` in the Terraform state file (`terraform.tfstate`).  Do the same for `mongodbatlas_cloud_provider_snapshot_restore_job` and `mongodbatlas_cloud_backup_snapshot_restore_job`.
+   **NOTE** Before performing any Terraform state change, please backup your state.
 
-5. Do a terraform plan (no changes detected)
+2. Upgrade the provider to v1.1.0.
+
+3. Run a `terraform plan` to ensure no changes are detected.
 
 ```bash
 terraform plan
 
 (...)
 
-
 No changes. Your infrastructure matches the configuration.
 
 Terraform has compared your real infrastructure against your configuration and found no differences,
 so no changes are needed.
 ```
 
-### Option 2: Replace the name of resource in terraform state
+### Option 2:  Remove the deprecated and import the new resources
+
+1. Remove your existing `mongodbatlas_cloud_provider_snapshot` and `mongodbatlas_cloud_provider_snapshot_restore_job` resources from the Terraform state file.
+   **NOTE** Before performing any Terraform state change, please backup your state.
+
+```bash
+$ terraform state rm mongodbatlas_cloud_provider_snapshot.test
+$ terraform state rm mongodbatlas_cloud_provider_snapshot_restore_job.test
+
+```
+
+2. Upgrade the provider to v1.1.0.
 
-1. Replace then name of the state in your existing `mongodbatlas_cloud_provider_snapshot` with `mongodbatlas_cloud_provider_snapshot` in terraform state file (`terraform.tfstate`).
-   **NOTE** before doing any terraform state change please do a backup
+3. Change your Terraform configuration file, replacing `mongodbatlas_cloud_provider_snapshot` with `mongodbatlas_cloud_backup_snapshot` and `mongodbatlas_cloud_provider_snapshot_restore_job` with `mongodbatlas_cloud_backup_snapshot_restore_job`.
 
-2. Change the version of provider to the v1.1.0
+4. Import your existing `mongodbatlas_cloud_provider_snapshot` to `mongodbatlas_cloud_backup_snapshot` and `mongodbatlas_cloud_provider_snapshot_restore_job` to `mongodbatlas_cloud_backup_snapshot_restore_job`:
+```bash
+    terraform import mongodbatlas_cloud_backup_snapshot.test <project_id>-<cluster_name>-<snapshot_id>
+```
+```bash
+    terraform import mongodbatlas_cloud_backup_snapshot_restore_job.test <project_id>-<cluster_name>-<job_id>
+```
 
-3. Do a terraform plan (no changes detected)
+5. Run a `terraform plan` to ensure no changes are detected.
 
 ```bash
 terraform plan
 
 (...)
 
-
 No changes. Your infrastructure matches the configuration.
 
 Terraform has compared your real infrastructure against your configuration and found no differences,
 so no changes are needed.
 ```
 
-**NOTE** Doc links for [mongodbatlas_cloud_backup_snapshot](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_backup_snapshot)
-
 ### Helpful Links
 
 * [Report bugs](https://github.com/mongodb/terraform-provider-mongodbatlas/issues)

website/docs/index.html.markdown

@@ -8,7 +8,7 @@ description: |-
 
 # MongoDB Atlas Provider
 
-You can use the MongoDB Atlas provider to interact with the resources supported by [MongoDB Atlas](https://www.mongodb.com/cloud/atlas). 
+You can use the MongoDB Atlas provider to interact with the resources supported by [MongoDB Atlas](https://www.mongodb.com/cloud/atlas).
 The provider needs to be configured with the proper credentials before it can be used.
 
 Use the navigation to the left to read about the available provider resources and data sources.
@@ -29,13 +29,16 @@ provider "mongodbatlas" {
 
 ## Configure Atlas Programmatic Access
 
-In order to set up authentication with the MongoDB Atlas provider a programmatic API key must be generated for MongoDB Atlas with the appropriate permissions and IP access list entries.
-The [MongoDB Atlas documentation](https://docs.atlas.mongodb.com/tutorial/manage-programmatic-access/index.html) contains the most up-to-date instructions for creating and managing your key(s) and IP access.
-Be aware, not all API resources require an IP access list by default, but one can set Atlas to require IP access entries for all API resources, see the [organization settings documentation](https://docs.atlas.mongodb.com/tutorial/manage-organization-settings/#require-ip-access-list-for-public-api) for more info.
+In order to set up authentication with the MongoDB Atlas provider, you must generate a programmatic API key for MongoDB Atlas with the appropriate [role](https://docs.atlas.mongodb.com/reference/user-roles/) and IP access list entries.
+The [MongoDB Atlas documentation](https://docs.atlas.mongodb.com/tutorial/manage-programmatic-access/index.html) contains the most up-to-date instructions for creating and managing your key(s), setting the appropriate role, and IP access.  
+
+**Role**: If unsure of which role level to grant your key, we suggest creating an organization API Key with an Organization Owner role. This ensures that you have sufficient access for all actions.
+
+**IP access list**: Some API resources, such as backup resources, require an IP access list by default. We highly suggest that you add an IP access list as soon as possible.  See [Require IP Access List for Public API](https://docs.atlas.mongodb.com/tutorial/manage-organization-settings/#require-ip-access-list-for-public-api) for more info.
 
 ## Authenticate the Provider
 
-The MongoDB Atlas provider offers a flexible means of providing credentials for authentication. 
+The MongoDB Atlas provider offers a flexible means of providing credentials for authentication.
 You can use any the following methods:
 
 ### Environment Variables
@@ -77,7 +80,7 @@ Consider the risks, especially the inadvertent submission of a configuration fil
 
 ## Argument Reference
 
-In addition to [generic `provider` arguments](https://www.terraform.io/docs/configuration/providers.html) 
+In addition to [generic `provider` arguments](https://www.terraform.io/docs/configuration/providers.html)
 (e.g. `alias` and `version`), the MongoDB Atlas `provider` supports the following arguments:
 
 * `public_key` - (Optional) This is the public key of your MongoDB Atlas API key pair. It must be
@@ -104,10 +107,9 @@ For more information on configuring and managing programmatic API Keys see the [
 
 ## Examples from MongoDB and the Community
 
-We have [example configurations](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/master/examples) 
+We have [example configurations](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/master/examples)
 in our GitHub repo that will help both beginner and more advanced users.
 
-Have a good example you've created and want to share? 
+Have a good example you've created and want to share?
 Let us know the details via an [issue](https://github.com/mongodb/terraform-provider-mongodbatlas/issues)
 or submit a PR of your work to add it to the `examples` directory in our [GitHub repo](https://github.com/mongodb/terraform-provider-mongodbatlas/).
-