Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
57 results found
-
Add a resource to configure the backup policy for Cloud Provider Snapshots
Please add support to change the backup policy for Cloud Provider Snapshots.
This is the API I am referring to:
https://docs.atlas.mongodb.com/reference/api/cloud-provider-snapshot-schedule-modify-one/Thanks.
6 votesThis is now out in version 0.5.1 of the provider. Once CPS in enabled the Atlas default schedule is imported and can be modified via terraform configuration (however if you chose to use the default no modification is needed). https://www.terraform.io/docs/providers/mongodbatlas/r/cloud_provider_snapshot_backup_policy.html
-
Add Terraform resource for custom database roles
Could we have a Terraform resource for creating custom database roles?
6 votesThis has been released in version 0.4.0
https://www.terraform.io/docs/providers/mongodbatlas/r/custom_db_role.htmlMore info on 0.4.0:
https://www.mongodb.com/blog/post/new-major-version-of-terraform-mongodb-atlas-providerThank you to community member Michał Paluchowski (https://github.com/mpaluchowski) for contributing to this resource!
-
Terraforming IP access list for project API key
The Terraform provider supports setting up IP access lists for organization API keys with "mongodbatlasaccesslistapikey". For project API keys, however, there is no way of managing IP access lists with Terraform, and we have to do it manually using the MongoDB Atlas UI.
Terraforming this is valuable because it would allow us to document the why and the what for each IP address or CIDR block. Having it in code will also increase the visibility of these access lists to the rest of the team, as changes to project API key access lists will be code-reviewed…
5 votes -
Atlas backup to second region in a Terraform Module
Feature for selecting "Atlas backup to second region" in Terraform Module.
Currently, this option is only supported by the UI and the API.4 votes -
MS Teams alert support in terraform provider
It is possible to configure MS Teams alerts in the atlas UI, however terraform support is still missing. It would be great to have that option
4 votesThis is now out in version 1.4.2.
-
Add possibility to invite api key(s) to newly created projects
For different types of automation, api key(s) must be added to project(s). It would be helpful if it could be possible to add existing api key(s) to new projects using
mongodbatlas\_project
terraform resource, example:
resource "mongodbatlas_project" "test" {
name = "project-name"
org_id = "<ORG\_ID>"teams {
team_id = "5e0fa8c99ccf641c722fe645"
role_names = ["GROUP_OWNER"]}
api_key {
public_key = "xyzxyzxy"
role_names = ["GROUP_READ_ONLY"]
}
}4 votesThis has been added as of version 1.2.0, released today. See https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project#api_key_id for more details. Thank you!
-
Terraform resource to provision maintenance windows
I propose creating a new terraform resource to provisioning maintenance windows.
This could be helpful to avoid setting this manually at the project level.
I'm new to Terraform but wouldn't mind to work on it, in case it makes sense.
Thanks
4 votesThis has been released in version 0.4.0
https://www.terraform.io/docs/providers/mongodbatlas/r/maintenance_window.htmlMore info on 0.4.0:
https://www.mongodb.com/blog/post/new-major-version-of-terraform-mongodb-atlas-provider -
Add sendCollectionLatencyMetrics and sendDatabaseMetrics switches for Datadog Integration
Atlas API supports (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration) two (relatively new) keys for Datadog integration:
*sendCollectionLatencyMetrics
*sendDatabaseMetrics
We need to have these switches in the terraform provider as well.
3 votesThis is now available in the Terraform provider as of terraform-provider-1.33.0. Thank you!
-
Push Logs to AWS S3 bucket: Terraform
Push Logs to AWS S3 bucket, This feature is helpful, It gives a flexibility for large organizations who need to segregate logs considering Inventory, Security and Observability to organize logs to a respective destinations from S3.However the terraform provider does have api's to fulfill this feature https://www.mongodb.com/docs/atlas/push-logs/ . If it can available in terms of terraform resources, This will help our organization to enable logging in terraform IAC to simplify the logging and deployments
3 votes -
Create option in terraform for keep backups after destruction
I saw that a feature was released to keep the backups of a cluster even if it was terminated. Basically the idea is to add a bool in terraform that does the work of activating or deactivating this feature, because whoever destroys the cluster using terraform does not have the option to keep the backup.
3 votesBackup Compliance Policy was released with v1.9.0 and Retain Backup flag is available in mongodbatlas_cluster and mongodbatlas_advanced_cluster in v1.10.0. Thank you for the feedback.
-
Allow configuration of Data Federation via Terraform
The
mongodbatlas_data_lake
(which should be renamed to reflect the new Data Federation name) doesn't allow you to specify the configuration. Without it, there is little value in having the resource defined in terraform at all.This issue: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/561 was created over a year ago to ask for this. A comment from MongoDB indicates its in the plan, just wanted to provide a vote for it.
3 votes -
mongodbatlas_serverless_privatelink_endpoint
I'm trying to import a serverless private link endpoint but I have no success with the current resource "mongodbatlasprivatelinkendpoint". As I investigate I saw that "mongodbatlasprivatelinkendpoint" is using the "private endpoint" API not the "serverless private endpoint" API reference on this url https://www.mongodb.com/docs/atlas/reference/api/serverless-private-endpoints/ that is why its unable to get the resource I wanted to import.
It is good if we have a separate resource for the serverless private endpoint because it is the only way to securely connect to AWS without using the network peering connection. As of this writing network peering is not yet…
3 votes -
Allow to assign API Key to Project via Terraform by referencing public key
Currently you can only assign an API Key to an Atlas Project via Terraform by referencing the ID of the API Key. Unfortunately, the ID is not exposed through the UI, only through the Atlas API. This is not very ideal for customers/users that are creating API Keys through the UI.
Adding support for referencing the API Key in Terraform via the public key instead of the ID would fix this. Or alternatively, exposing the API Key ID in Atlas.
3 votesWe released support for Data Source: mongodbatlas_api_keys which exposes the api_key_id paramter as part of v1.8.0. Thank you for the feedback.
For more details see: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/data-sources/api_keys#api_key_id
-
Enable the use of AWS PrivateLink in Terraform
MongoDB Atlas provides the ability to configure AWS PrivateLink to connect customer VPCs with MongoDB Atlas. I would like to see this capability exposed through Terraform.
3 votesThis has been released in version 0.4.0
https://www.terraform.io/docs/providers/mongodbatlas/r/private_endpoint.html
and
https://www.terraform.io/docs/providers/mongodbatlas/r/private_endpoint_interface_link.htmlMore info on 0.4.0:
https://www.mongodb.com/blog/post/new-major-version-of-terraform-mongodb-atlas-provider -
atlas terrafrom mongodbatlas_encryption_at_rest
It would be great to have secrets as sensitive fields in the "mongodbatlasencryptionatrest" terraform resource such as client secrets, secretaccess_key, etc. Otherwise they show as plain text in the console/stdout. I understand they will still be stored in the state file, but at least they are removed from logs.
3 votesAll of the sensitive fields should now be marked as such in the code base for the provider. If any others are found please file an issue at:
https://github.com/mongodb/terraform-provider-mongodbatlas/issuesThank you!
-
Disable data explorer and other features in project settings
The following features cannot be disabled in the terraform provider (project settings):
Real Time Performance Panel
Data Explorer
Performance Advisor and Profiler
Schema Advisor2 votesThe project settings can now be set via the project resource in the provider. Thank you!
-
Allow Management of Identity Providers through Terraform
The necessary API endpoints appear to exist, it would be great to expose them in the Terraform provider for Atlas to avoid having a split between Infrastructure-as-Code and having to browse the web interface.
2 votesThis is now out in version 1.4.2
-
Ability to create GovCloud projects
Need ability to "Designate as a Gov Cloud regions-only project" when creating projects in order to allow subsequently creating clusters in Gov Cloud regions
2 votes -
Create Snapshot Export Bucket using Terraform
Create Snapshot Export Bucket using Terraform- required to export Snapshots to S3.
Implement the following API call by the provider:
POST /groups/{GROUP-ID}/backup/exportBucketshttps://docs.atlas.mongodb.com/reference/api/cloud-backup/export/create-one-export-bucket/
2 votesThis feature is now available in version 1.3.0 of the provider.
-
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 completed and in v0.9.0 of the provider.
- Don't see your idea?