Skip to content

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

41 results found

  1. Use cluster id as app_id when creating a trigger via terraform

    We would like to specify the cluster id as appid inside the mongodbatlasevent_trigger resources in order to match the trigger creation available via gui

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Terraform data source for Point in Time Recovery

    It has been confirmed by MongoDB support, that in Atlas, there is no way to know the last point in time you can recover a cluster to using OpsLogs. Surely this is an oversight, as we should be able to tell, from the backup material available, what point in time we can recover to, and not just from.

    I need to automate a restoration of a cluster into another cluster in another project in a second region. I copy backup material, including OpsLogs, to that region. I would like to be able to use Terraform to get the Unix Timestamp,…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. The IPs of the newly created cluster should be in the terraform state directly

    We are trying to deploy a cluster in Azure using Terraform and then inspect the newly created cluster to get the hostnames and IP addresses. We need these IP Addresses so we update the Azure Firewall to allow the Azure Key Vault to communicate with the Atlas cluster. We are doing this test to enable encryption at rest with our own keys.

    We believe the IPs should be in the terraform state directly.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Terraform provider should handle pagination for mongodbatlas_atlas_users resource

    The resource mongodbatlasatlasusers limits results returned by page with a default of 100 and max of 500. Attempting to retrieve a complete list of users where that list is not a known size isn't possible because of Terraform limitations on dynamic blocks. It would be quite helpful if the Terraform provider handled pagination and this resource by default returned a complete list.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Support tags in terraform-provider-mongodbatlas mongodbatlas_project

    terraform-provider-mongodbatlas mongodbatlas_project doesn't currently support tags.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Terraform Downward Autoscaling "Use Smallest possible" placeholder

    When setting "providerautoscalingcomputemininstancesize", is it possible to either;

    • Loosen the validation by ignoring current disk configuration size.
    • Create a placeholder to indicate "Use smallest possible value".

    Atlas appears to support invalid values, provided it was entered when it was valid.


    I think this will help simplify deployment of "providerautoscalingcomputemininstancesize", we set the ideal value and THE MACHINE will interpret the best match and remove the possibility of a once valid Terraform definition becoming invalid without any updates on the definition. Like the following example,
    1. I define an…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Reestablish private endpoint if in status "Rejected"

    Create an AWS endpoint for connection with the (already established) MongoDB Atlas endpoint service -> AWS endpoint is in "Pending acceptance" status.
    Establish the connection with "mongodbatlasprivatelinkendpointservice" -> AWS endpoint goes into "Available" status.
    Destroy the "mongodbatlas
    privatelinkendpointservice" connection -> AWS endpoint goes into "Rejected" status.
    Recreate "mongodbatlasprivatelinkendpoint_service" with the same variables -> terraform does recreate he resource, but the resource is not functional.
    In the MongoDB Atlas GUI it shows "Failed. Endpoint failed to reach available state. Click 'Edit' to fix the problem."
    The problem cannot be fixed by using "Edit" !

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Reference existing third party integration in alert configuration notifications

    Provide a mechanism that enables referencing an existing atlas third party integration when using the alert configuration resource to create or update a third party notification.
    This is useful when a third party integration is imported or accessed through a data source, meaning the api token is not available. An example of this would be Slack integration as it has to be created through the Atlas UI using OAuth2, so the api token cannot be accessed in the terraform configuration.

    More details in: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1074

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Support Auto-Resume in Trigger resource

    can we have an autoresume argument in mongodbatlaseventtrigger (https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/eventtrigger)?

    as in the screenshot, Auto-Resume suspended trigger can be switched on in Atlas UI.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Uniform approach to Dedicated and Tenant clusters in terraform mongodbatlas_advanced_cluster

    Our software development lifecycle has 5 environments. We also wish to spin up dedicated, short lived environments for individual Developers. As a result, we'd like to have two M40s, an M10 and two M5s for our SDLC and the ability to spin up M0s for the devs.

    The way you've implemented the terraform mongodbadvancedcluster resource makes it exceptionally difficult to use the same code across all environments. This isn't in keeping with best practice for terraform implementations, which is to use the same code and only change the variables. Might I suggest you add providertype and allow

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Ability to update x509 certificate via the Terraform provider mongodbatlas_x509_authentication_database_user

    Provide the ability to create a new certificate when it is close to expiration.
    We currently create a database User using - mongodbatlasx509authenticationdatabaseuser

    Tthere is no way to generate a new certificate and update the Secret manager/Vault with this.

    Via Terraform (automated)

    I am currently updating the resource name to force Terraform to do this.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Add Terraform support for Device Sync

    Device Sync (https://www.mongodb.com/docs/atlas/app-services/sync/get-started/) can't be managed via Terraform. This would be a great addition to the provider!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. upload prebuilt typescript provider for cdktf support

    I am trying to add the mongodb/mongodbatlas provider to a newly created cdktf project generated in the typescript language but the installation fails as npm is unable to find a prebuilt cdktf provider for the provider

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. mongodbatlas_database_connection

    A resource that creates a connection for a database.

    resource "mongodbatlas_database_connection" "connection" {
      database        = "test"     # Name of database
      connection_type = "Standard" # or Private Endpoint
      database_user   = "test"     # Name of DB_USER
      method          = "shell"    # other options  "application | compass | vscode"
    
      # For Standard Connection
      ip = "accessAnywhere" # or other IP Address
    
      # For Private Endpoint
      endpoint = "" # ID of Private Endpoint
    }
    
    

    OUTPUT ARGUMENTS

    • id
    • connection_string
    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add support for profile configuration file in the Terraform provider

    To be able to quickly change which account we use for the Terraform provider without having the keys in the terraform variables, supporting profile config file like what aws does for it's provider would be a great help for us.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. mongodbatlas_cloud_backup_snapshot_restore_job should wait until the restore operation is complete

    mongodbatlascloudbackupsnapshotrestorejob creates a job and returns immediately , but I think it should wait until the restore operation is complete. just like mongodbatlascluster that waits until the cluster is in ready state.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Allow setting of advanced server parameters such as disable flow control, ttlMonitor and redactClientLogData

    For some more advanced/demanding use cases, advanced server parameters are key to provide the performance/latency or security that applications will require, either due to contractual or complaince obligations.

    FlowControl throttles writes for consistency sake, but for very low latency use cases it becomes a factor for "perceived" client SLO breach. In such particular scenarios, the cost consistent across all replicas is higher than low latency reply.

    redactClientLogData is important to ensure complaince with several sectors such has identity management.

    TTL monitor should be able to be controled via API call to better manage the migrations between self-managed clusters and Atlas.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Allow provider-level configuration for project in Atlas terraform provider

    For the provider-level configuration, would be nice to be able to set the project at provider level vs. having to provide it at resource level.

    Currently, it doesn't seem that the provider accepts a project argument.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base