43 results found

1. Support ISRG certificate selection in mongodbatlas_cluster

   As described in https://docs.atlas.mongodb.com/reference/faq/security/ and a recent email announcement, the root certificate is changing. Changing the cert used is available in the UI, but not in the provider.

   It would be useful to add support for certificate selection.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Terraform Provider  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Ideally migration of terraform state should be handled or provide a tool for migrating state

   Hello,
   We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.

   Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.

   Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.

   ============================================

   There are warnings related to your configuration. If no errors occurred,
   Terraform will continue despite these warnings. It is a good idea to resolve
   these warnings in the near future.

   Warnings:
   module.mongodbatlasds.mongodbatlasprivateendpoint.atlasprivateendpoint: this resource is deprecated, please transition as soon as possible to mongodbatlasprivatelinkendpoint
   module.mongodbatlasds.mongodbatlasprivateendpointinterfacelink.atlasprivateendpointinterfacelink: this resource is deprecated, please transition as soon as possible to mongodbatlasprivatelinkendpoint_service

   We did try using the import example but unfortunately ran into this issue:

   Error importing: Provider "mongodbatlas" depends on non-var "data.external.mongoatlasvaultcredentials.0/data.external.mongoatlasvaultcredentials.N". Providers for import can currently only depend on variables or must be hardcoded. You can stop import from loading configurations by specifying -config="".

   https://github.com/hashicorp/terraform/issues/17847

   Our provider configuration is something like this where it pulls the credentials from vault using a script:
   provider"mongodbatlas"{
   version="0.8.2"
   publickey="${data.external.mongoatlasvaultcredentials.result.publickey}"
   privatekey="${data.external.mongoatlasvaultcredentials.result.privatekey}"
   }

   Now just for the sake of trying, I did hard code the pubic key/private key in the provider for my dev dc and in that case, the import does work as expected. But since we have 10 data centers for which we have different keys, it's not possible for us to hard code anything since the same code is used for all the DCs. So even though the import option can work for a simple deployment test, it's not a working solution for us.

   Hello,
   We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.

   Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.

   Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.

   ============================================

   There are warnings related to your configuration. If no… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Terraform Provider  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Indicate operation errors already in the plan phase

   This idea originates from my original bug report: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/284

   Changing the name of an existing custom_db_role is currently not possible without ending in an error in the apply step. The plan for a name change currently indicates the replacement due to the name change:

   # module.versioner.mongodbatlas_custom_db_role.this must be replaced
   -/+ resource "mongodbatlas_custom_db_role" "this" {
       ~ id         = "someid" -> (known after apply)
           project_id = "5c860ed2a6f2396cd47f4785"
       ~ role_name  = "old_name" -> "newName" # forces replacement
   

   Applying this results in the following error:

   Error: error deleting custom db role (mongoversioner): DELETE https://cloud.mongodb.com/api/atlas/v1.0/groups/projectid/customDBRoles/roles/old_name: 409 (request "Conflict") Deleting specified custom role would leave the following users without a role: someuser.

   I understand that this is not possible directly without unassigning the user, but some indication for these kinds of issues already in the plan phase would make things much easier to handle.

   This idea originates from my original bug report: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/284

   Changing the name of an existing custom_db_role is currently not possible without ending in an error in the apply step. The plan for a name change currently indicates the replacement due to the name change:

   # module.versioner.mongodbatlas_custom_db_role.this must be replaced
   -/+ resource "mongodbatlas_custom_db_role" "this" {
       ~ id         = "someid" -> (known after apply)
           project_id = "5c860ed2a6f2396cd47f4785"
       ~ role_name  = "old_name" -> "newName" # forces replacement
   

   Applying this results in the following error:

   Error: error deleting custom db role (mongoversioner): DELETE https://cloud.mongodb.com/api/atlas/v1.0/groups/projectid/customDBRoles/roles/old_name: 409 (request "Conflict") Deleting specified custom role would leave the… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Terraform Provider  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close