Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. LDAP configuration using Terraform

    We would like to be able to use Terraform to configure LDAP authentication/authorization on projects.

    The functionality is available via the API:
    https://docs.atlas.mongodb.com/reference/api/ldaps-configuration/

    However, go-client-mongodb-atlas does not have these endpoints implemented, so that would need to be done before this functionality is included in the provider.

    28 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  2. Possibility to change 'frequency_type' of snapshot backup policy item via Terraform

    Hi,

    I’m facing an issue about Snapshot Backup Policy creation/modification via Terraform ( FYI, I open a case to the support of MongoDB  https://support.mongodb.com/case/00668262). Let me explain :

    When I want to create a MongoAtlas Cluster via terraform, I want to apply a custom Snahsphot Backup Policy with ONLY 2 items during the creation of the cluster :
    N° Item Frequency type Frequency Retention
    0 Daily 1 7 Days
    1 Weekly 1 (Saturday) 4 weeks

    However, during the creation of the mongo atlas cluster, I can see an error
    Error: Error applying plan:

    1 error occurred:

    * module.cluster_contrib.module.dpjmongoatlas.module.tfmodule-gcp-mongo-atlas-cluster.mongodbatlas_cloud_provider_snapshot_backup_policy.snapshot_backup:
    21 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow Atlas clusters to be paused using terraform

    The ability to pause Atlas clusters through terraform would help with being able to pause our non-prod environments when not in use. Currently this has to be managed directly with the Atlas API

    18 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  4. Create databases and collections via API thorough Terraform

    Create databases (DB) and collections via API thorough Terraform after the cluster has been created in Atlas. This would provide the ease of writing and running it in a single script before any data is loaded.

    15 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow creation of Atlas organizations in Terraform

    there are really 3 steps for our dev teams to get moving in Atlas:
    1. create an org
    2. create a project
    3. create a cluster
    the first one is the only one that still has to be done from a console. if we had a terraform script to create an org in our account, we could trigger creation after approval in ServiceNow

    8 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  6. A terraform resource for managing user access to the console

    We have a platform (as code using Terraform) where we integrate Mongo Atlas in AWS. We have multiple teams with various privileges who access the Mongo Atlas console daily basis. We would always like to manage the users in our version control. As Terraform is one of the best infrastructure configuration tools, we would like to have a terraform resource in order to manage the users via.

    6 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ability to create/update triggers using terraform

    Ability to create/update triggers using terraform

    5 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  8. Adding indexes using terraform

    Ability to add indexes after new clusters are created using Terraform and data has been loaded. It will help in more automation and auto recovery.

    5 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  9. Create collections and indexes on cluster creation

    Allow creation of collections and indexes via terraform atlas plugin. The use case is that, when an atlas cluster is being set up, we want to enable the indexes on the collections from the start.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  10. create collection in new project

    Please create functionality for operating data in collections of MongoDB

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  11. Provide an option to disable password auth for database users

    Currently, it is not possible securely create a user in a terraform DevOps pipeline, since "Passwords may show up in Terraform related logs" according to the documentation. If the password was no longer required to create a user, we could avoid this issue by only using certificate authentication.

    1 vote
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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…

    1 vote
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base