Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
54 results found
-
Terraform provider should handle pagination for mongodbatlas_atlas_users resource
The resource mongodbatlasatlasusers limits results returned by page with a default of 100 and max of 500. Attempting to retrieve a complete list of users where that list is not a known size isn't possible because of Terraform limitations on dynamic blocks. It would be quite helpful if the Terraform provider handled pagination and this resource by default returned a complete list.
1 vote -
Terraform Downward Autoscaling "Use Smallest possible" placeholder
When setting "providerautoscalingcomputemininstancesize", is it possible to either;
- Loosen the validation by ignoring current disk configuration size.
- Create a placeholder to indicate "Use smallest possible value".
Atlas appears to support invalid values, provided it was entered when it was valid.
I think this will help simplify deployment of "providerautoscalingcomputemininstancesize", we set the ideal value and THE MACHINE will interpret the best match and remove the possibility of a once valid Terraform definition becoming invalid without any updates on the definition. Like the following example,
1. I define an…1 vote -
Reestablish private endpoint if in status "Rejected"
Create an AWS endpoint for connection with the (already established) MongoDB Atlas endpoint service -> AWS endpoint is in "Pending acceptance" status.
Establish the connection with "mongodbatlasprivatelinkendpointservice" -> AWS endpoint goes into "Available" status.
Destroy the "mongodbatlasprivatelinkendpointservice" connection -> AWS endpoint goes into "Rejected" status.
Recreate "mongodbatlasprivatelinkendpoint_service" with the same variables -> terraform does recreate he resource, but the resource is not functional.
In the MongoDB Atlas GUI it shows "Failed. Endpoint failed to reach available state. Click 'Edit' to fix the problem."
The problem cannot be fixed by using "Edit" !…
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 -
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 -
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
- Don't see your idea?