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
-
Support Slack in Third Party Integration
Slack is supported via UI or API, but not via the Terraform Provider (v1.3.1).
9 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 -
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/5688MongoDB Support mentioned we could use the AWS KMS which supports automatic key rotation.
So we are suggesting implementing…
6 votes -
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_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 -
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 editing default project alerts via terraform
For instance, the default Query Targeting alert is set at a 1000:1 ratio. I would like to have the default alert set to 5000:1 for a project via terraform.
6 votes -
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!
24 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 -
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 -
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 -
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 -
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 -
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 -
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 -
Indicate operation errors already in the plan phase
This idea originates from my original bug report: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/284
Changing the name of an existing
custom_db_roleis currently not possible without ending in an error in theapplystep. The plan for a name change currently indicates the replacement due to the name change:# module.versioner.mongodbatlas_custom_db_role.this must be replaced -/+ resource "mongodbatlas_custom_db_role" "this" { ~ id = "someid" -> (known after apply) project_id = "5c860ed2a6f2396cd47f4785" ~ role_name = "old_name" -> "newName" # forces replacementApplying this results in the following error:
Error: error deleting custom db role (mongoversioner): DELETE https://cloud.mongodb.com/api/atlas/v1.0/groups/projectid/customDBRoles/roles/old_name: 409 (request "Conflict") Deleting specified custom role would leave the…
1 vote -
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.
31 votes -
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.
92 votes
- Don't see your idea?