mongodb
diff --git a/‎.github/workflows/examples.yml‎
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/examples.yml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github_changelog_generator‎
Lines changed: 2 additions & 2 deletions b/‎.github_changelog_generator‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎CHANGELOG.md‎
Lines changed: 15 additions & 0 deletions b/‎CHANGELOG.md‎
Lines changed: 15 additions & 0 deletions
diff --git a/‎examples/atlas-api-key/README.md‎
Lines changed: 18 additions & 0 deletions b/‎examples/atlas-api-key/README.md‎
Lines changed: 18 additions & 0 deletions
diff --git a/‎examples/atlas-api-key/create-and-assign-pak-seperately/README.md‎
Lines changed: 14 additions & 0 deletions b/‎examples/atlas-api-key/create-and-assign-pak-seperately/README.md‎
Lines changed: 14 additions & 0 deletions
diff --git a/‎examples/atlas-api-key/create-and-assign-pak-seperately/main.tf‎
Lines changed: 32 additions & 0 deletions b/‎examples/atlas-api-key/create-and-assign-pak-seperately/main.tf‎
Lines changed: 32 additions & 0 deletions
diff --git a/‎examples/atlas-api-key/create-and-assign-pak-seperately/provider.tf‎
Lines changed: 4 additions & 0 deletions b/‎examples/atlas-api-key/create-and-assign-pak-seperately/provider.tf‎
Lines changed: 4 additions & 0 deletions
diff --git a/‎examples/atlas-api-key/create-and-assign-pak-seperately/variables.tf‎
Lines changed: 10 additions & 0 deletions b/‎examples/atlas-api-key/create-and-assign-pak-seperately/variables.tf‎
Lines changed: 10 additions & 0 deletions
diff --git a/‎examples/atlas-api-key/create-and-assign-pak-seperately/versions.tf‎
Lines changed: 8 additions & 0 deletions b/‎examples/atlas-api-key/create-and-assign-pak-seperately/versions.tf‎
Lines changed: 8 additions & 0 deletions
diff --git a/‎examples/atlas-api-key/create-and-assign-pak-together/README.md‎
Lines changed: 13 additions & 0 deletions b/‎examples/atlas-api-key/create-and-assign-pak-together/README.md‎
Lines changed: 13 additions & 0 deletions
@@ -17,7 +17,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        terraform_version: ["0.13.0"]
+        terraform_version: ["0.15.0"]
     steps:
       - uses: actions/checkout@v3
         with:
 
@@ -1,4 +1,4 @@
-future-release=v1.9.0
-since-tag=v1.8.2
+future-release=v1.10.0
+since-tag=v1.9.0
 date-format=%B %d, %Y
 base=CHANGELOG.md
@@ -1,5 +1,20 @@
 # Changelog
 
+## [v1.10.0](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/v1.10.0) (June 10, 2023)
+
+[Full Changelog](https://github.com/mongodb/terraform-provider-mongodbatlas/compare/v1.9.0...v1.10.0)
+
+**Closed issues:**
+
+- Online Archive: "Specified cloud provider is not supported in Data Lake Storage" but works in UI [\#1216](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1216)
+- Asymmetric hardware is not supported by the provider [\#1214](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1214)
+- `region` argument missing from `mongodbatlas_third_party_integration` for integration with PagerDuty [\#1180](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1180)
+- Correct docs for importing network peering resources [\#1179](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1179)
+- Terraform destroy produces a 500 \(UNEXPECTED\_ERROR\) on the underlying API call [\#1162](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1162)
+- produced an unexpected new value: Root resource was present, but now │ absent [\#1160](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1160)
+- Failed to respond to the plugin.\(\*GRPCProvider\).PlanResourceChange call [\#1136](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1136)
+- Error: error creating MongoDB Cluster: unexpected EOF [\#674](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/674)
+
 ## [v1.9.0](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/v1.9.0) (2023-4-27)
 
 [Full Changelog](https://github.com/mongodb/terraform-provider-mongodbatlas/compare/v1.8.2...v1.9.0)
 
@@ -0,0 +1,18 @@
+# MongoDB Atlas Provider -- MongoDB Atlas Programmatic API Key Examples 
+
+In the Terraform MongoDB Atlas Provider v1.8.0 release, we introduced support for MongoDB Atlas Programmatic API Keys (PAK). While this was an exciting development, we quickly realized that some of our customers were facing challenges in optimally leveraging this resource. In response to this, we initiated several enhancements as part of the v1.10.0 release to refine the user experience with this resource. These enhancements encompassed both code revisions and documentation updates.
+
+The most notable improvement among these as part of v1.10.0 release was the deprecation of the `api_keys` parameter from the `mongodbatlas_project` resource. We also extended the functionality of the `mongodbatlas_project_api_key` resource by incorporating the `project_assignment` parameter. This enhancement removes the necessity for users to create multiple `mongodbatlas_project` resource blocks just to assign keys. This update streamlines the process of assigning an API Key to multiple projects, making it less cumbersome and more manageable.
+
+To further facilitate the transition, we've included in this atlas-api-key folder, three reference examples for Programmatic API Key (PAK) usage:
+
+* "Create and Assign PAK Together" — this demonstrates how to create a PAK and assign it simultaneously.
+
+* "Create and Assign PAK to Multiple Projects" — this shows how to create a PAK and assign it to several projects at once.
+
+* "Create and Assign PAK Separately" (Deprecated) — this is an older method of creating and assigning PAKs, now deprecated but still available for reference.
+
+Lastly, in MongoDB Atlas, all PAKs are Organization API keys. Once created, a PAK are linked at the organization level with an 'Organization Member' role. However, these Organization API keys can also be assigned to one or more projects within the organization. When a PAK is assigned to a specific project, it essentially takes on the 'Project Owner' role for that particular project. This enables the key to perform operations at the project level, in addition to the organization level. The flexibility of PAKs provides a powerful mechanism for fine-grained access and control, once their functioning is clearly understood. 
+
+Our hope is that these examples will provide clear guidance and help ease your transition to this new PAK workflow in our Terraform Provider.
+
@@ -0,0 +1,14 @@
+# MongoDB Atlas Provider -- Create and Assign PAK Separately (Deprecated) 
+
+Note this functionality has been deprecated and will be removed in v1.12.0. Instead suggest see examples for Create and Assign PAK Together + Create and Assign PAK to Multiple Projects.
+This example creates an organization API Key and access list, showing how to attach a CIDR block.
+
+Variables Required to be set:
+- `project_id`: ID of the Atlas project
+- `org_id`: ID of Atlas organization
+- `public_key`: Atlas public key
+- `private_key`: Atlas  private key
+
+In this example, we will set up an organization API key and attach an access list to it.
+**Note:** in this example parameter api_keys is deprecated and will be removed in v1.12.0 release from codebase. Use `mongodbatlas_project_api_key`  resource instead. 
+
@@ -0,0 +1,32 @@
+
+# Create Programmatic API Key
+resource "mongodbatlas_api_key" "orgKey1" {
+  description = "orgKey2"
+  org_id      = var.org_id
+  role_names  = ["ORG_OWNER"]
+}
+
+# Assign Newly Created Programmatic API Key to Project 
+resource "mongodbatlas_project" "test2" {
+  name   = "testorgapikey"
+  org_id = var.org_id
+
+  api_keys {
+    api_key_id = mongodbatlas_api_key.orgKey1.api_key_id
+    role_names = ["GROUP_OWNER"]
+  }
+
+  /* ensure this assignment gets cleaned up if the organization key created with api_key is deleted.  api_keys block would still need to be removed from the terraform config file */
+  depends_on = [
+    mongodbatlas_api_key.orgKey1
+  ]
+
+}
+
+# Add IP Access List Entry to Programmatic API Key 
+resource "mongodbatlas_access_list_api_key" "test3" {
+  org_id     = var.org_id
+  cidr_block = "0.0.0.0/1"
+  api_key_id = mongodbatlas_api_key.orgKey1.api_key_id
+}
+
@@ -0,0 +1,4 @@
+provider "mongodbatlas" {
+  public_key  = var.public_key
+  private_key = var.private_key
+}
@@ -0,0 +1,10 @@
+variable "public_key" {
+  description = "Public API key to authenticate to Atlas"
+}
+variable "private_key" {
+  description = "Private API key to authenticate to Atlas"
+}
+variable "org_id" {
+  description = "Atlas organization id"
+  default     = ""
+}
@@ -0,0 +1,8 @@
+terraform {
+  required_providers {
+    mongodbatlas = {
+      source = "mongodb/mongodbatlas"
+    }
+  }
+  required_version = ">= 0.13"
+}
@@ -0,0 +1,13 @@
+# MongoDB Atlas Provider -- Create and Assign PAK together
+This example creates a project API Key and access list, showing how to attach a CIDR block.
+
+Variables Required to be set:
+- `project_id`: ID of the Atlas project
+- `org_id`: ID of Atlas organization
+- `public_key`: Atlas public key
+- `private_key`: Atlas  private key
+
+In this example, we will set up a project API key and attach an access list to it.
+
+
+**Note:** in this example parameter role_names is deprecated and will be removed in v1.12.0 release from codebase. Use `project_assignment`  parameter instead.