Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
LDAP configuration using Terraform
We would like to be able to use Terraform to configure LDAP authentication/authorization on projects.
The functionality is available via the API:
https://docs.atlas.mongodb.com/reference/api/ldaps-configuration/However, go-client-mongodb-atlas does not have these endpoints implemented, so that would need to be done before this functionality is included in the provider.
36 votes -
Possibility to change 'frequency_type' of snapshot backup policy item via Terraform
Hi,
I’m facing an issue about Snapshot Backup Policy creation/modification via Terraform ( FYI, I open a case to the support of MongoDB https://support.mongodb.com/case/00668262). Let me explain :
When I want to create a MongoAtlas Cluster via terraform, I want to apply a custom Snahsphot Backup Policy with ONLY 2 items during the creation of the cluster :
N° Item Frequency type Frequency Retention
0 Daily 1 7 Days
1 Weekly 1 (Saturday) 4 weeksHowever, during the creation of the mongo atlas cluster, I can see an error
Error: Error applying plan:1 error occurred:
…* module.cluster_contrib.module.dpjmongoatlas.module.tfmodule-gcp-mongo-atlas-cluster.mongodbatlas_cloud_provider_snapshot_backup_policy.snapshot_backup:
26 votes -
Allow Atlas clusters to be paused using terraform
The ability to pause Atlas clusters through terraform would help with being able to pause our non-prod environments when not in use. Currently this has to be managed directly with the Atlas API
22 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.
21 votes -
Allow creation of Atlas organizations in Terraform
there are really 3 steps for our dev teams to get moving in Atlas:
1. create an org
2. create a project
3. create a cluster
the first one is the only one that still has to be done from a console. if we had a terraform script to create an org in our account, we could trigger creation after approval in ServiceNow16 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.
14 votes -
Add option to create project without alerts
Currently a project is created with a set of default alerts. We need to customize these but we can only add new alerts via terraform. It would be helpful if there was a boolean flag in the mongodbatlas_project resource to disable default alert creation
13 votes -
Ability to create/update triggers using terraform
Ability to create/update triggers using terraform
10 votesWe are reviewing adding support for triggers and will update here if we firm up addition of it in the roadmap. Thank you!
-
Add resource to allow attachment of roles to mongodbatlas_cloud_provider_access
The need to do two applies to completely configure the
mongodbatlas_cloud_provider_access
resource should have never seen the light of day. I would like to see an additional resource that could attach a role to amongodbatlas_cloud_provider_access
after it has been created. Then you could use the attributes in themongodbatlas_cloud_provider_access
resource to create the role, then attach the role to it using theaccess_role_attachment
resource.9 votes -
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.
8 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.4 votes -
Create collections and indexes on cluster creation
Allow creation of collections and indexes via terraform atlas plugin. The use case is that, when an atlas cluster is being set up, we want to enable the indexes on the collections from the start.
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_enabled2 votes -
Support the regions parameter of a network peering container
In the API documentation you mention a regions parameter usable when creating a network container with a network smaller than /18. In terraform there is no such parameter. I would like to see that supported (for creating networks smaller than /18 on GCP).
See: https://docs.atlas.mongodb.com/reference/api/vpc-create-container/#request-body-parameters
2 votesThis work is planned. Sometimes features release in Atlas and there is a lag to support in Terraform.
-
create collection in new project
Please create functionality for operating data in collections of MongoDB
2 votes -
1 vote
-
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.
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 -
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.
1 vote -
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.
1 vote
- Don't see your idea?