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
-
Add sendCollectionLatencyMetrics and sendDatabaseMetrics to third_party_integration
Could you introduce sendCollectionLatencyMetrics and sendDatabaseMetrics to the tf provider defined in API spec https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration
1 vote -
Add extended JSON to mongodbatlas_event_trigger
Although it is possible to enable EJSON via the UI (and API), it would be best to do it with the mongodbatlaseventtrigger resource itself
1 vote -
Manage Organization Alerts in Terraform
We should be able to manage organization alerts through terraform, not only project level alerts.
I wanted to create a billing alert at organization level with terraform but was not able to do it, because the resource only allows the alert to be created at project level.
Doc: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/alert_configuration1 vote -
Provide state import capability on mongodbatlas_organization resource
The mongodbatlas_organization resource does not have state import capabilities and I don't understand why. This doesn't seem to be a difficult one to implement and for us it will greatly help, because we have a need to import into state existing organisations which were created (unfortunately) outside terraform.
10 votes -
Update the regex used to split a database user import id to match the database name constraint
Hello,
While doing terraform import of the mongo db users, i'm facing an issue with the mongo terraform provider.
The database name contains an underscore so my imported user ID is 5ceClusterId-username-my_database.
I've got the following error when i launch my terraform import:
Error: error splitting database User info from ID
│ import format error: to import a Database User, use the format {projectid}-{username}-{authdatabase_name}Indeed the mongo tf provider uses a regex to split this ID and doesn't allow characters for db name others than $a-z.
=> https://github.com/mongodb/terraform-provider-mongodbatlas/blob/ebb67f86165e0a364e486e769678377db507f005/internal/service/databaseuser/resource_database_user.go#L349Is it possible to update the regex to allow others…
5 votes -
OIDC Authentication Terraform Provider
Hi,
it should be possible to authenticate with a service account from Entra ID to MongDB Atlas with the Usage of OIDC.
Here is an example of this in azurerm: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/service_principal_oidcpros:
- no password / private key needed
- no rotation of credentials needed1 vote -
Adding description in user database using Terraform
I'm not able to set description on user database using terraform. This feature is available on API but not in the terraform provider.
6 votes -
Add boolean for applying changes only during maintenance window
Add boolean for applying changes only during maintenance window in order to not affect workloads during peak periods.
E.g.: we want to modify the instance type of our cluster, but we don't want to affect workloads during the day, therefore, any change to the cluster should be applied only during maintenance hours. The same functionality should be available in the console. As a matter of fact, all changes should be by default applied during maintenance window and user can choose to opt out and apply them immediately.
See DocumentDB as an example for this feature.
https://docs.aws.amazon.com/documentdb/latest/developerguide/db-instance-modify.html3 votes -
We would need the GCP project number associated with a certain Atlas project
We would need the GCP project number associated with a certain Atlas project. Preferably we would need this integrated in the Terraform provider and in an API.
Having the GCP project number corresponding to a certain Atlas project would allow ACL creation with the various features provided by the cloud provider.0 votes -
mongodbatlas_cloud_backup_snapshot_restore_job
Add waitforcompletion field to mongodbatlascloudbackupsnapshotrestore_job to wait untile restore job has finished
1 vote -
Configuring provider with shared credentials file for secrets manager
Currently the provider allows configuration for secrets manager for the API key, however it looks like only static AWS credentials can be used which require assuming a role first and exporting environment variables. It would be much cleaner if you could support shared profiles, much like the AWS provider does https://registry.terraform.io/providers/hashicorp/aws/latest/docs#profile-1.
https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html
Specifically https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/internal/provider/credentials.go#L49 is static credentials, but would be great to add profile as an option as well.5 votes -
Implement the role mapping for the MongoDB atlas teams to the Projects Using terraform
Currently terraform supports to assign single user invitation with role assignment to the projects, however we do not see any role assignment enabled for the teams & API keys.
We would like to know whether this feature can be enabled in coming versions or if we have any alternative/workaround solutions please share with us.
1 vote -
Expose just the server name (without the rest of the connection string) as a cluster attribute
There are many
connection_stringsavailable, but all of them are a full URI. Since the canonical way to connect is with the login and password in the URI, I always need to parse the value of aconnection_strings, insert login info, and then reformat it.I'd like to just have the server name available as an attribute.
1 vote -
Control shard balancing window with Terraform
This documentation page talks about how to manage shard balancing - https://www.mongodb.com/docs/manual/tutorial/manage-sharded-cluster-balancer/#schedule-the-balancing-window
but it requires connecting to the db first, I see no way to manage this through the Atlas Gui or terraform.
We have had some instances recently where shard balancing has caused a large resource usage spike on our cluster and affected our services and we would really like to be able to set a shard balancing window using terraform to prevent this from happening during the middle of the day2 votes -
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 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 tags in terraform-provider-mongodbatlas mongodbatlas_project
terraform-provider-mongodbatlas mongodbatlas_project doesn't currently support tags.
2 votes -
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 -
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 -
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
- Don't see your idea?