Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
40 results found
-
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.
103 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.
37 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.
36 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!
28 votes -
Add Terraform resource for functions
Would be great to have a terraform resource like mongodbatlas_function.
Was mentioned here https://github.com/mongodb/terraform-provider-mongodbatlas/issues/828 but I didn't find the idea mentioned there, so I added this one here.21 votes -
Adding indexes(Not search index) using terraform
I would like to create mongodb atlas index using terraform. But as of now we can able to create search index in mongodb atlas using terraform. here the expectation is to create normal index using terraform.
18 votes -
Terraform support for Database Triggers using Function events
The Database Triggers resource supports only EventBridge right now. It would be awesome to see support for Function events as well
16 votesHi we working to enhance the the use of Triggers and Functions in Terraform, but this effort still several quarters away. Feel free to reach on in the interim in case of any questions and happy to help.
-
Support Slack in Third Party Integration
Slack is supported via UI or API, but not via the Terraform Provider (v1.3.1).
10 votes -
Add the ability to configure the auto-resume setting for triggers through terraform
Currently MongoDB triggers can be created through the TF, but to enabled the auto-resume setting this needs to be manually done through the Atlas UI. This should be an option on the "mongodbatlaseventtrigger" TF resource, so it can be all configured together.
9 votes -
Create Atlas App Services and Link Them To Clusters with Terraform
It would be great to create App Services (Realm Apps) and then create the service link to an Atlas Cluster with Terraform.
This is so that Trigger resources can be created fully within Terraform, rather than having to hack together API calls, CLI commands or manual steps.
6 votes -
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.
6 votes -
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 -
Terraform lifecycle ignore_changes tags
It would be nice if tags would not be set of list and will be a map, like tags for Azure resources.
In that case, you can ignore some tags by name. Like thislifecycle {
ignore_changes = [
tags["costcenter"],
tags["environment"],
tags["projectcode"]
]
}https://github.com/mongodb/terraform-provider-mongodbatlas/issues/2006
4 votes -
Support terraform plan with ORG_READ_ONLY role
An API key with ORGREADONLY should be sufficient to run a terraform plan. Afterall its describe is "Provides read-only access to the settings, users, projects, and billing in the organization.")
However, this is not the case: checking settings for "Cloud Provider Access" [1] and "Encrypting at Rest" [2] fail due to mission permission. Read-write project permissions like GROUP_OWNER on each project are required.[1] https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Provider-Access/operation/listCloudProviderAccessRoles
[2] https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Encryption-at-Rest-using-Customer-Key-Management/operation/getEncryptionAtRest4 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…4 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.
4 votes -
Use cluster id as app_id when creating a trigger via terraform
We would like to specify the cluster id as appid inside the mongodbatlasevent_trigger resources in order to match the trigger creation available via gui
3 votes -
Reference existing third party integration in alert configuration notifications
Provide a mechanism that enables referencing an existing atlas third party integration when using the alert configuration resource to create or update a third party notification.
This is useful when a third party integration is imported or accessed through a data source, meaning the api token is not available. An example of this would be Slack integration as it has to be created through the Atlas UI using OAuth2, so the api token cannot be accessed in the terraform configuration.More details in: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1074
3 votes -
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
3 votes -
Add a data source for the Atlas Control Plane inbound/outbound IPs
It would be nice to be able to fetch all outbound and inbound IPs for the Atlas control plane so that we can add them to the list of allowed IPs on Azure keyvaults for example
3 votes
- Don't see your idea?