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
-
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 Teams to a Project
Allow to add a team to a project and set roles.
Split the creation of the project and the role assignment.
Based on the API: https://www.mongodb.com/docs/atlas/reference/api/project-add-team/6 votes -
Support Slack in Third Party Integration
Slack is supported via UI or API, but not via the Terraform Provider (v1.3.1).
9 votes -
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 -
A way to enable the Data API via Terraform
I just noticed that MongoDB Data API is no longer in beta (Congrats!). It think it would be quite useful if the there was a way to enable this option programmatically via Terraform.
5 votes -
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 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 -
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_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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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?