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

9 results found

  1. Pausing MongoDB Atlas Cluster with option of start/end time

    There is a parameter available for cluster resource to pause the cluster. With this parameter, we have to flip the status from pause to unpause whenever needed.

    I am looking for separate resource (like maintenance window) where one can configure to pause the cluster for specific window (start/end time)

    Example: I want to pause all non-prod clusters by Friday evening 5 PM EST and resume the cluster 7 AM EST. With trigger it is possible, but we do have hundreds of deployments. It would be great if we have resource where customer can specify their own timing to pause and…

    15 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    declined  ·  3 comments  ·  Terraform Provider  ·  Admin →

  2. MongoDb cloud Atlas terraform plugin for Oracle Cloud Infrastructure(OCI)

    Hello Team,
    Looking forward to collaborating with MongoDb Cloud Atlas team to develop a custom-ready terraform plugin for Oracle Cloud Infrastructure similar to the ones we have for AWS, Azure, and GCP. Currently, we are deploying Mongo DB clusters in OCI IAAS. The plugin we develop will be really helpful for OCI customers who would like to have their MongoDB deployed on OCI platform. Looking forward to a positive revert.

    15 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Terraform Provider  ·  Admin →

  3. Ability to create/update a temporary Database user using terraform

    Hi
    Presently, we can only create permanent database users via Terraform Modules. The creation of temporary DB users is only allowed through the UI or by consuming MongoDb Atlas's APIs. In addition, the "deleteAfterDate" property is only applicable for a temporary user already existent. The point is to avoid using "null_resource" and "local-exec" in our Terraform Modules.

    8 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    declined  ·  1 comment  ·  Terraform Provider  ·  Admin →

  4. Atlas does not automatically rotate the Key Version Resource ID used for Google Cloud key management.

    Basically, when a new version of the key is being created in GCP, Atlas Terraform provider does not accept primary or newest value for version argument.

    We cannot use the data source to filter on the version that is primary or the "newest" https://registry.terraform.io/providers/hashicorp/google/latest/docs/data-sources/kms_crypto_key_version, it will default to 1. We have to specify the version #. But we need this to be fully automated.

    I found this issue which seems to show the same situation, but it’s from 2020…
    https://github.com/hashicorp/terraform-provider-google/issues/5688

    MongoDB Support mentioned we could use the AWS KMS which supports automatic key rotation.

    So we are suggesting implementing…

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    declined  ·  1 comment  ·  Terraform Provider  ·  Admin →

  5. Standardize case for region values

    Depending on the resource, the case for the region value changes from uppercase with underscores (US_ EAST _1) to lowercase with dashes (us-east-1). This presents an unnecessary challenge when working with the provider. It would be much cleaner, easier to work with, and prone to fewer errors if all resources accepted us-east-1.

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    declined  ·  3 comments  ·  Terraform Provider  ·  Admin →

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

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    declined  ·  2 comments  ·  Terraform Provider  ·  Admin →

  7. mongodbatlas_cluster should wait until cluster is operational

    mongodbatlas_cluster is regarded "created" before it's operational, which breaks things if you need to use attributes that aren't yet available, like connection_strings.

    This issue is acknowledged in the provider docs:

    connection_strings - Set of connection strings that your applications use to connect to this cluster. More info in Connection-strings. Use the parameters in this object to connect your applications to this cluster. To learn more about the formats of connection strings, see Connection String Options. NOTE: Atlas returns the contents of this object after the cluster is operational, not while it builds the cluster.

    (...)

    Private connection strings may…

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    declined  ·  1 comment  ·  Terraform Provider  ·  Admin →

  8. Allow Database User Password Encryption

    There should be a way to encrypt the password for database user resource. Currently, it's optional, so either you need to reset or create the password manually or via rest Api's. There shouldn't be two different methods to configure one resource.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Admin →
    declined  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    Note the database password is not optional. Additional information was not provided so not sure of the specifics of the request (assuming it may be perhaps longer term management of the password?). If there are any questions around this resource feel free to reach out directly. Also the MongoDB Atlas Vault plugin could be useful for those looking for ephemeral secrete management: https://www.mongodb.com/atlas/hashicorp-vault. Thank you!

  9. Remove limit for sending invitations terraform-provider-mongodbatla

    Remove limit for sending invitations using the terraform plugin terraform-provider-mongodbatla. Currnetly there is a limit of sending 10 invitations per minute per IP. That makes this plugin pretty much useless.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    declined  ·  2 comments  ·  Terraform Provider  ·  Admin →
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)