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

59 results found

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

    6 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. Provide state import capability on mongodbatlas_organization resource

    The mongodbatlas_organization resource does not have state import capabilities and I don't understand why. This doesn't seem to be a difficult one to implement and for us it will greatly help, because we have a need to import into state existing organisations which were created (unfortunately) outside terraform.

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

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

    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. Configuring provider with shared credentials file for secrets manager

    Currently the provider allows configuration for secrets manager for the API key, however it looks like only static AWS credentials can be used which require assuming a role first and exporting environment variables. It would be much cleaner if you could support shared profiles, much like the AWS provider does https://registry.terraform.io/providers/hashicorp/aws/latest/docs#profile-1.
    https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html
    Specifically https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/internal/provider/credentials.go#L49 is static credentials, but would be great to add profile as an option as well.

    7 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)
  6. Update the regex used to split a database user import id to match the database name constraint

    Hello,

    While doing terraform import of the mongo db users, i'm facing an issue with the mongo terraform provider.

    The database name contains an underscore so my imported user ID is 5ceClusterId-username-my_database.

    I've got the following error when i launch my terraform import:
    Error: error splitting database User info from ID
    │ import format error: to import a Database User, use the format {projectid}-{username}-{authdatabase_name}

    Indeed the mongo tf provider uses a regex to split this ID and doesn't allow characters for db name others than $a-z.
    => https://github.com/mongodb/terraform-provider-mongodbatlas/blob/ebb67f86165e0a364e486e769678377db507f005/internal/service/databaseuser/resource_database_user.go#L349

    Is it possible to update the regex to allow others…

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

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

    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. federated authentication to terraform provider

    Allow OIDC authentication to the terraform provider to eliminate the need for secrets or static configuration

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

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

    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. mongodbatlas_federated_database_instance add GCP support

    Is GCP support planned for terraform provider and GCP?

    dataprocessregion {
    cloudprovider = "GCP"
    region = "IOWA
    USA"
    }

    Trying to use this in Terraform results in 500 Internal Server Error

    │ Error: error creating MongoDB Atlas Federated Database Instace: https://cloud.mongodb.com/api/atlas/v2/groups/***/dataFederation POST: HTTP 500 Internal Server Error (Error code: "UNEXPECTED_ERROR") Detail: Unexpected error. Reason: Internal Server Error.

    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. 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. Add extended JSON to mongodbatlas_event_trigger

    Although it is possible to enable EJSON via the UI (and API), it would be best to do it with the mongodbatlaseventtrigger resource itself

    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. OIDC Authentication Terraform Provider

    Hi,

    it should be possible to authenticate with a service account from Entra ID to MongDB Atlas with the Usage of OIDC.
    Here is an example of this in azurerm: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/service_principal_oidc

    pros:
    - no password / private key needed
    - no rotation of credentials needed

    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. We would need the GCP project number associated with a certain Atlas project

    We would need the GCP project number associated with a certain Atlas project. Preferably we would need this integrated in the Terraform provider and in an API.
    Having the GCP project number corresponding to a certain Atlas project would allow ACL creation with the various features provided by the cloud provider.

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

    Add waitforcompletion field to mongodbatlascloudbackupsnapshotrestore_job to wait untile restore job has finished

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

    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. Implement the role mapping for the MongoDB atlas teams to the Projects Using terraform

    Currently terraform supports to assign single user invitation with role assignment to the projects, however we do not see any role assignment enabled for the teams & API keys.

    We would like to know whether this feature can be enabled in coming versions or if we have any alternative/workaround solutions please share with us.

    https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project_invitation

    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. Terraform lifecycle ignore_changes tags

    It would be nice if tags would not be set of list and will be a map, like tags for Azure resources.
    In that case, you can ignore some tags by name. Like this

    lifecycle {
    ignore_changes = [
    tags["costcenter"],
    tags["environment"],
    tags["projectcode"]
    ]
    }

    https://github.com/mongodb/terraform-provider-mongodbatlas/issues/2006

    4 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)
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base