Skip to content

Atlas

← MongoDB Feedback Engine
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

How can we improve the platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

61 results found

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

    4 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  2. Add boolean for applying changes only during maintenance window

    Add boolean for applying changes only during maintenance window in order to not affect workloads during peak periods.

    E.g.: we want to modify the instance type of our cluster, but we don't want to affect workloads during the day, therefore, any change to the cluster should be applied only during maintenance hours. The same functionality should be available in the console. As a matter of fact, all changes should be by default applied during maintenance window and user can choose to opt out and apply them immediately.

    See DocumentDB as an example for this feature.
    https://docs.aws.amazon.com/documentdb/latest/developerguide/db-instance-modify.html

    3 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

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

    3 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

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

    3 votes
    planned  ·  2 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  5. Manage federated database views via Terraform

    The mongodbatlasfederateddatabase_instance resource allows managing tables in the federated instance, but it does not allow us to manage views. Please update the provider so we can also create and manage views

    3 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  6. 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
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

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

    3 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  8. Use Semantic Versioning

    Hi,

    My problem is that the terraform provider doesn't use semantic versioning.

    This has caused me quite a few problems.
    Firstly - it's difficult when scrolling through your version releases to understand what's breaking and what's not (I lost an hour today having to check all the releases for updates, and then applying every couple of versions from an outdated provider to make sure there were no breaking changes).
    Secondly, it means I have to pin a specific version in my terraform provider rather than leaving it to auto-update to the latest minor version "~> 1.0".
    Lastly, it makes using…

    2 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  9. Create One Rolling Index in Terraform

    This is a request to add our One Rolling Index request to our Terraform.

    References:
    * https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Rolling-Index/operation/createRollingIndex

    Benefits:

    Many teams interact with Atlas via automation using Terraform. This has been highlighted as one of the important ones to have in Terraform.

    2 votes
    1 comment  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  10. Add sendCollectionLatencyMetrics and sendDatabaseMetrics switches for Datadog Integration

    Atlas API supports (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration) two (relatively new) keys for Datadog integration:
    * sendCollectionLatencyMetrics
    * sendDatabaseMetrics

    We need to have these switches in the terraform provider as well.

    2 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  11. Allow API key with project owner rights the update of project API keys

    We would like to use the terraform provider mongodbatlas_access_list_api_key to maintain the access list of our existing API keys.
    We don't have an API key with organization owner rights. We have only an API key with project owner rights.
    When I do the changes via web ui project owner rights are enough. I don't understand why the terraform provider needs organization owner rights.
    In my understanding it should be possible to execute the provider mongodbatlas_access_list_api_key also with project owner rights.

    2 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  12. Manage Organization Alerts in Terraform

    We should be able to manage organization alerts through terraform, not only project level alerts.
    I wanted to create a billing alert at organization level with terraform but was not able to do it, because the resource only allows the alert to be created at project level.
    Doc: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/alert_configuration

    2 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  13. Control shard balancing window with Terraform

    This documentation page talks about how to manage shard balancing - https://www.mongodb.com/docs/manual/tutorial/manage-sharded-cluster-balancer/#schedule-the-balancing-window
    but it requires connecting to the db first, I see no way to manage this through the Atlas Gui or terraform.
    We have had some instances recently where shard balancing has caused a large resource usage spike on our cluster and affected our services and we would really like to be able to set a shard balancing window using terraform to prevent this from happening during the middle of the day

    2 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  14. Support tags in terraform-provider-mongodbatlas mongodbatlas_project

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

    2 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  15. 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" !

    …

    2 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

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

    2 votes
    2 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  17. 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
    1 comment  ·  Terraform Provider  ·  Admin →
    How important is this to you?

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

    2 votes
    2 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  19. Use Semantic Versioning

    Hi,

    My problem is that the terraform provider doesn't use semantic versioning.

    This has caused me quite a few problems.
    Firstly - it's difficult when scrolling through your version releases to understand what's breaking and what's not (I lost an hour today having to check all the releases for updates, and then applying every couple of versions from an outdated provider to make sure there were no breaking changes).
    Secondly, it means I have to pin a specific version in my terraform provider rather than leaving it to auto-update to the latest minor version "~> 1.0".
    Lastly, it makes using…

    1 vote
    planned  ·  2 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  20. Add support for ephemeral password input in mongodbatlas_database_user resources

    Terraform v1.10 added ephemeral resources that are not persisted in state, and v1.11 then added support for write-only resource attributes. To make use of this new resource type, resources must take a write-only input for applicable variables.

    To make use of this in mongodbatlas_database_user, I propose adding an alternative password_wo input that is mutually exclusive with the existing password input, along with a supplementary password_wo_version value that will trigger a change if required (this is the pattern used in aws_secretsmanager_secret_version).

    The database user could then be configured as such, without the password being present in the terraform state:

    …
    1 vote
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?
2 4
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)