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

37 results found

  1. Terraform support for Database Triggers using Function events

    The Database Triggers resource supports only EventBridge right now. It would be awesome to see support for Function events as well

    12 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)

    Hi we working to enhance the the use of Triggers and Functions in Terraform, but this effort still several quarters away. Feel free to reach on in the interim in case of any questions and happy to help. 

  2. Support Slack in Third Party Integration

    Slack is supported via UI or API, but not via the Terraform Provider (v1.3.1).

    9 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. Make the app_id optional in the mongodbatlas_event_trigger resource when an aws_eventbridge event processor is defined

    Currently, when you define a trigger that uses the AWS Eventbridge via the UI it auto creates a realm App that links the DB change to the event bridge.

    However, with the mongodbatlaseventtrigger resource you have to manually defined an empty realm app and give the resource the app_id of that empty app.

    This is obviously not a 100% automated process.

    This could be, if the provider created the empty realm app by itself, then referencing the created app app_id.

    This would only be needed:
    1. when the appid is not provided
    2. the following attribute was

    3 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. 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)
  5. 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)
  6. 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)
  7. Add Terraform support for Realm Apps

    Realm Apps (https://docs.mongodb.com/realm/get-started/create-realm-app/) can't be managed via Terraform. This would be a great addition to the provider!

    26 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)
  8. 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)
  9. 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)
  10. For resource mongodbatlas_cluster all properties related to provider move to separate block

    Current resource

    resource "mongodbatlas_cluster" "cluster" {
      project_id   = var.project_id
      name         = var.cluster_name
      disk_size_gb = var.disk_size_gb
      num_shards   = var.num_shards
      replication_factor           = var.replication_factor
      auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled
      mongo_db_major_version       = var.mongo_db_major_version
      //Provider Settings "block"
      provider_name               = var.provider_name
      provider_disk_iops          = var.provider_disk_iops
      provider_volume_type        = var.provider_volume_type
      provider_instance_size_name = var.provider_instance_size_name
      provider_region_name        = var.provider_region_name
      provider_backup_enabled      = var.provider_backup_enabled
    }
    

    Suggested resource

    resource "mongodbatlas_cluster" "cluster" {
      project_id   = var.project_id
      name         = var.cluster_name
      disk_size_gb = var.disk_size_gb
      num_shards   = var.num_shards
      replication_factor           = var.replication_factor
      auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled
      mongo_db_major_version       = var.mongo_db_major_version
      //Provider Settings "block"
      cluster_provider = {
        name               = var.provider_name
        disk_iops          = var.provider_disk_iops
        volume_type        = var.provider_volume_type
        instance_size_name = var.provider_instance_size_name
        region_name        = var.provider_region_name
        backup_enabled     = var.provider_backup_enabled
    3 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)
  11. Attach a newly created Trigger to an existing AWS Event Bridge Bus via Terraform.

    Attach a newly created Trigger to an existing AWS Event Bridge Bus via Terraform.

    3 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)
  12. 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)
  13. 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)
  14. 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…

    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. 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.

    35 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)
  16. 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.

    100 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)
  17. 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.

    35 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 Next →
  • Don't see your idea?

Feedback and Knowledge Base