Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
41 results found
-
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 -
mongodbatlas_cluster should wait until cluster is operational
mongodbatlas_clusteris regarded "created" before it's operational, which breaks things if you need to use attributes that aren't yet available, likeconnection_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 -
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_enabled3 votes -
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 -
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 -
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 -
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 -
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
1 vote -
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 -
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 -
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 - mongodbatlasx509authenticationdatabaseuserTthere 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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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
- Don't see your idea?