v1.8.0 CHANGELOG and UpgradeGuide (#1024)

* Create 1.8.0-upgrade-guide.html.markdown

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md

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

Co-authored-by: Melissa Plunkett <[email protected]>

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

Co-authored-by: Melissa Plunkett <[email protected]>

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

Co-authored-by: Melissa Plunkett <[email protected]>

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

* third_party_integrations_update

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

Co-authored-by: Melissa Plunkett <[email protected]>

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

Co-authored-by: Melissa Plunkett <[email protected]>

* Update 1.8.0-upgrade-guide.html.markdown

* warning update

* Update CHANGELOG.md

* Update 1.8.0-upgrade-guide.html.markdown

* Update 1.8.0-upgrade-guide.html.markdown

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

Co-authored-by: Melissa Plunkett <[email protected]>

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

Co-authored-by: Melissa Plunkett <[email protected]>

* Update CHANGELOG.md

Co-authored-by: Melissa Plunkett <[email protected]>

Author: Zuhairahmed

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## [v1.8.0](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/v1.8.0) (2023-1-23)
+## [v1.8.0](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/v1.8.0) (2023-1-25)
 
 [Full Changelog](https://github.com/mongodb/terraform-provider-mongodbatlas/compare/v1.7.0...v1.8.0)
 
@@ -9,9 +9,9 @@
 - Snapshot Distribution Support [\#979](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/979) - INTMDB-400
 - Programmatically Create API Keys [\#974](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/974) - INTMDB-346
 - Retrieve `org_id` from API Keys [\#973](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/973) - INTMDB-454
+- `oplogMinRetentionHours` Parameter Support in `advanced_cluster` and `cluster` resources [\#1016](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1016) - INTMDB-397
 - Analytics Node Tier New Features Support [\#994](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/994) - INTMDB-488
 - Improve Default Alerts and Example Creation [\#993](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/993) - INTMDB-382
-- `oplogMinRetentionHours` Paramter Support in `advanced_cluster` and `cluster` resources [\#1016](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1016) - INTMDB-397
 - Expand documentation for `cloud_backup_schedule` to include information about valid values for `frequency_interval` [\#1007](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1007) - INTMDB-547
 
 **Depreciations:**
@@ -24,8 +24,8 @@
 - Hide `current_certificate` when X.509 Authentication Database Users are Created [\#985](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/985) - INTMDB-468
 - Import example added for `encryption_at_rest` resource [\#992](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/992) - INTMDB-530 
 - Resource `cloud_backup_snapshot_export_job` variable name change [\#976](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/976) - INTMDB-523
-- Invitation handling after user accepts invitation fix [\#1012](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1012) - INTMDB-511 
 - `update_snapshot` doesn't save at TF state with `cloud_backup_schedule` resource fix [\#974](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/974) - INTMDB-472
+- Invitation handling after user accepts invitation fix [\#1012](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1012) - INTMDB-511 
 - `bi_connector` settings in `advanced_cluster` fix (breaking changes) [\#1010](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1010) - INTMDB-455
 - `third_party_integration` api_token keeps updating on every apply fix [\#1011](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1011) - INTMDB-519
 - `custom_db_role` error fix [\#1009](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1009) - INTMDB-448
@@ -45,7 +45,7 @@
 
 - Chore\(deps\): Bump github.com/gruntwork-io/terratest from 0.41.7 to 0.41.9 [\#1013](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1013) ([dependabot[bot]](https://github.com/apps/dependabot))
 
-## [v1.7.0](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/v1.7.0) (2022-12-23)
+## [v1.7.0](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/v1.7.0) (2023-1-16)
 
 [Full Changelog](https://github.com/mongodb/terraform-provider-mongodbatlas/compare/v1.6.1...v1.7.0)
 

website/docs/d/access_list_api_key.html.markdown

@@ -15,6 +15,8 @@ description: |-
 ~> **IMPORTANT:**
 When you remove an entry from the access list, existing connections from the removed address(es) may remain open for a variable amount of time. How much time passes before Atlas closes the connection depends on several factors, including how the connection was established, the particular behavior of the application or driver using the address, and the connection protocol (e.g., TCP or UDP). This is particularly important to consider when changing an existing IP address or CIDR block as they cannot be updated via the Provider (comments can however), hence a change will force the destruction and recreation of entries.   
 
+~> **IMPORTANT WARNING:** Managing Atlas Programmatic API Keys (PAKs) with Terraform will expose sensitive organizational secrets in Terraform's state. We suggest following [Terraform's best practices](https://developer.hashicorp.com/terraform/language/state/sensitive-data). You may also want to consider managing your PAKs via a more secure method, such as the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
+
 
 ## Example Usage
 

website/docs/d/access_list_api_keys.html.markdown

@@ -15,6 +15,7 @@ description: |-
 ~> **IMPORTANT:**
 When you remove an entry from the access list, existing connections from the removed address(es) may remain open for a variable amount of time. How much time passes before Atlas closes the connection depends on several factors, including how the connection was established, the particular behavior of the application or driver using the address, and the connection protocol (e.g., TCP or UDP). This is particularly important to consider when changing an existing IP address or CIDR block as they cannot be updated via the Provider (comments can however), hence a change will force the destruction and recreation of entries.   
 
+~> **IMPORTANT WARNING:** Managing Atlas Programmatic API Keys (PAKs) with Terraform will expose sensitive organizational secrets in Terraform's state. We suggest following [Terraform's best practices](https://developer.hashicorp.com/terraform/language/state/sensitive-data). You may also want to consider managing your PAKs via a more secure method, such as the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
 
 ## Example Usage
 

website/docs/d/api_key.html.markdown

@@ -10,7 +10,7 @@ description: |-
 
 `mongodbatlas_api_key` describes a MongoDB Atlas API Key. This represents a API Key that has been created.
 
-~> **IMPORTANT WARNING:**  Creating, Reading, Updating, or Deleting Atlas API Keys may key expose sensitive organizational secrets to Terraform State. For best security practices consider storing sensitive API Key secrets instead via the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
+~> **IMPORTANT WARNING:** Managing Atlas Programmatic API Keys (PAKs) with Terraform will expose sensitive organizational secrets in Terraform's state. We suggest following [Terraform's best practices](https://developer.hashicorp.com/terraform/language/state/sensitive-data). You may also want to consider managing your PAKs via a more secure method, such as the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
 
 -> **NOTE:** You may find org_id in the official documentation.
 

website/docs/d/api_keys.html.markdown

@@ -10,7 +10,7 @@ description: |-
 
 `mongodbatlas_api_keys` describe all API Keys. This represents API Keys that have been created.
 
-~> **IMPORTANT WARNING:**  Creating, Reading, Updating, or Deleting Atlas API Keys may key expose sensitive organizational secrets to Terraform State. Consider storing sensitive API Key secrets instead via the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
+~> **IMPORTANT WARNING:** Managing Atlas Programmatic API Keys (PAKs) with Terraform will expose sensitive organizational secrets in Terraform's state. We suggest following [Terraform's best practices](https://developer.hashicorp.com/terraform/language/state/sensitive-data). You may also want to consider managing your PAKs via a more secure method, such as the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
 
 -> **NOTE:** Groups and projects are synonymous terms. You may find `groupId` in the official documentation.
 

website/docs/d/project_api_key.html.markdown

@@ -10,7 +10,7 @@ description: |-
 
 `mongodbatlas_project_api_key` describes a MongoDB Atlas Project API Key. This represents a Project API Key that has been created.
 
-~> **IMPORTANT WARNING:**  Creating, Reading, Updating, or Deleting Atlas API Keys may key expose sensitive organizational secrets to Terraform State. For best security practices consider storing sensitive API Key secrets instead via the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
+~> **IMPORTANT WARNING:** Managing Atlas Programmatic API Keys (PAKs) with Terraform will expose sensitive organizational secrets in Terraform's state. We suggest following [Terraform's best practices](https://developer.hashicorp.com/terraform/language/state/sensitive-data). You may also want to consider managing your PAKs via a more secure method, such as the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
 
 -> **NOTE:** You may find project_id in the official documentation.
 

website/docs/d/project_api_keys.html.markdown

@@ -10,7 +10,7 @@ description: |-
 
 `mongodbatlas_api_keys` describe all API Keys. This represents API Keys that have been created.
 
-~> **IMPORTANT WARNING:**  Creating, Reading, Updating, or Deleting Atlas API Keys may key expose sensitive organizational secrets to Terraform State. Consider storing sensitive API Key secrets instead via the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
+~> **IMPORTANT WARNING:** Managing Atlas Programmatic API Keys (PAKs) with Terraform will expose sensitive organizational secrets in Terraform's state. We suggest following [Terraform's best practices](https://developer.hashicorp.com/terraform/language/state/sensitive-data). You may also want to consider managing your PAKs via a more secure method, such as the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas).
 
 -> **NOTE:** Groups and projects are synonymous terms. You may find `groupId` in the official documentation.
 

website/docs/d/third_party_integration.markdown

@@ -35,14 +35,16 @@ data "mongodbatlas_third_party_integration" "test" {
 * `type`       - (Required) Third-Party service integration type
      * PAGER_DUTY
      * DATADOG
-     * NEW_RELIC
+     * NEW_RELIC*
      * OPS_GENIE
      * VICTOR_OPS
-     * FLOWDOCK
+     * FLOWDOCK*
      * WEBHOOK
      * MICROSOFT_TEAMS
      * PROMETHEUS
 
+     *resource is now deprecated and will be removed in the next major version, 1.9.0
+
 
 ## Attributes Reference
 

website/docs/d/third_party_integrations.markdown

@@ -52,6 +52,18 @@ In addition to all arguments above, the following attributes are exported:
 * `project_id`  - (Required) ID of the Atlas project the Third-Party Service Integration belongs to.
 * `type`        - (Required) Thirt-Party service integration type.
 
+     * PAGER_DUTY
+     * DATADOG
+     * NEW_RELIC*
+     * OPS_GENIE
+     * VICTOR_OPS
+     * FLOWDOCK*
+     * WEBHOOK
+     * MICROSOFT_TEAMS
+     * PROMETHEUS
+
+     *resource is now deprecated and will be removed in the next major version, 1.9.0
+
 Additional values based on Type
 
 * `PAGER_DUTY`

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

@@ -0,0 +1,39 @@
+---
+layout: "mongodbatlas"
+page_title: "MongoDB Atlas Provider 1.8.0: Upgrade and Information Guide"
+sidebar_current: "docs-mongodbatlas-guides-180-upgrade-guide"
+description: |-
+MongoDB Atlas Provider 1.8.0: Upgrade and Information Guide
+---
+
+# MongoDB Atlas Provider 1.8.0: Upgrade and Information Guide
+
+The Terraform MongoDB Atlas Provider version 1.8.0 has a number of new and exciting features and changes.
+
+**New Features:**
+* You can now enable and manage backup [snapshot distribution](https://www.mongodb.com/blog/post/introducing-snapshot-distribution-atlas) with [`mongodbatlas_cloud_backup_schedule`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_backup_schedule)
+* You can now manage the lifecycle of your [Programmatic API Keys](https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Programmatic-API-Keys) [`mongodbatlas_api_key`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/api_key) 
+  *  **IMPORTANT WARNING:**  Managing Atlas Programmatic API Keys (PAKs) with Terraform will expose sensitive organizational secrets in Terraform's state.  We suggest following [Terraform's best practices](https://developer.hashicorp.com/terraform/language/state/sensitive-data).  You may also want to consider managing your PAKs via a more secure method, such as the [HashiCorp Vault MongoDB Atlas Secrets Engine](https://developer.hashicorp.com/vault/docs/secrets/mongodbatlas). 
+* You can now retrieve `org_id` from API Keys with [`mongodbatlas_roles_org_id`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/data-sources/roles_org_id)
+* You can now set the [`oplogMinRetentionHours`](https://www.mongodb.com/docs/upcoming/reference/configuration-options/#mongodb-setting-storage.oplogMinRetentionHours) parameter in [`mongodbatlas_advanced_cluster`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/advanced_cluster) and [`mongodbatlas_cluster`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cluster) resources  
+
+
+**Changes:**
+* `current_certificate` is now hidden when [`mongodbatlas_x509_authentication_database_user`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/x509_authentication_database_user) is created
+* Expanded documentation for [`cloud_backup_schedule`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_backup_schedule) to include information about valid values for `frequency_interval`
+
+**Depreciations:**
+* [`mongodbatlas_cloud_provider_snapshot`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_provider_snapshot), [`mongodbatlas_cloud_provider_snapshot_backup_policy`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_provider_snapshot_backup_policy), [`mongodbatlas_cloud_provider_snapshot_restore_job`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_provider_snapshot_restore_job) have been deprecated for a few versions.  We will proceed with removal in the next major version, 1.9.0.  They have been replaced by [`mongodbatlas_cloud_backup_snapshot`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_backup_snapshot), [`mongodbatlas_cloud_backup_schedule`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_backup_schedule), [`mongodbatlas_cloud_backup_snapshot_restore_job`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_backup_snapshot_restore_job), respectively. 
+* [`mongodbatlas_private_ip_mode`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/private_ip_mode) has been deprecated for a few versions.  We will proceed with removal in the next major version, 1.9.0.  
+* NEW_RELIC and FLOWDOCK in the [`mongodbatlas_third_party_integration`](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/third_party_integration#argument-reference) resource are now deprecated and will be removed in the next major version, 1.9.0.
+
+1.8.0 also includes general improvements, bug fixes, and several key documentation updates. See the [CHANGELOG](https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/CHANGELOG.md) for more specific information.
+
+
+### Helpful Links
+
+* [Report bugs](https://github.com/mongodb/terraform-provider-mongodbatlas/issues)
+
+* [Request Features](https://feedback.mongodb.com/forums/924145-atlas?category_id=370723)
+
+* [Contact Support](https://docs.atlas.mongodb.com/support/) covered by MongoDB Atlas support plans, Developer and above.