AdminMelissa
(Lead Product Manager, MongoDB)
My feedback
19 results found
-
15 votes
An error occurred while saving the comment -
31 votes
An error occurred while saving the comment Stefan, there is still no underlying endpoints in the Atlas Admin API that allow full control of the index lifecycle so we have no plans at this time to add index management to Terraform (there is one to allow only creation of an index in a rolling fashion but we would be unable to update or delete that index via the admin API). Indexes can be created via scripts or the shell as part of your CI/CD process.
If this changes we will update the status of this feedback. Thank you,
Melissa -
6 votes
An error occurred while saving the comment We already have Teams: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/team and the team is added to the project: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project. Are you asking for something different? If not we'll close this as already completed. Thanks!
-
6 votes
An error occurred while saving the comment Hi Sebastian and Scott, I'm curious if CDK for Terraform may fulfill your requirements? It's my understanding that it should work with any existing Terraform provider but we have not yet tested it with ours: https://github.com/hashicorp/terraform-cdk. Or are you looking specifically for CDK for CloudFormation?
-
1 vote
An error occurred while saving the comment Hi Mohammad, Thank you for the submission. Due to the variability of the length of restore jobs, some can take significant amounts of time, we currently have no plans to wait until the job is complete as users have specifically not wanted to wait on the return. If you can share more about your use case and how this would be helpful to you it would help.
-
3 votes
An error occurred while saving the comment Hi Gus, Thank you for the submission. The provider does wait until the cluster creation is complete before it returns. The note on connection_strings is more about the status of the value being empty until the cluster is fully created, e.g. if you run Terraform on the command line you'll see the status of the cluster continue to print till it is done, Terraform won't actually have the value for connection_strings till that part is completed. We'd had users try to get and use that value before the cluster was completed and hence the docs add. There are times some connection strings can't be known even when the cluster itself is created, and that's when using private connections. The second note you have here is about that. We have no plans to wait till that is fully populated as users we've spoken with, in general, did not feel it was necessary. If that's actually what you are asking for - for the provider to wait until the private connection is completed and all connection strings are known - you may want to narrow it down to that use case.
-
6 votes
An error occurred while saving the comment There is now an option to create a project with no default alerts (https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project#with_default_alerts_settings) so that you can define them all within Terraform. Another option is to import in the existing alerts and then modify them. Hope this is helpful.
-
8 votes
An error occurred while saving the comment Thank you Nikola! Very helpful.
An error occurred while saving the comment I'm the Product Manager for the agent and it would be great to know what distro of linux you require support for, for example Amazon Linux 2, RHEL, etc. Feel free to comment here or reach out to me directly, melissa.plunkett@mongodb.com. Thank you!
-
4 votes
An error occurred while saving the comment This exists for Atlas: https://docs.mongodb.com/mongocli/stable/command/mongocli-atlas-customDbRoles/
-
2 votes
An error occurred while saving the comment Thank you for the submission, however we already added this feature about a year ago. In the "review and deploy" window OM 4.4+ will warn if a change is likely to cause a restart with "These changes will cause processes to undergo a safe, rolling restart." Is there perhaps a specific case where you did not get this message?
-
16 votes
An error occurred while saving the comment Thank you for the submission. Within Atlas we are able to offer this feature as all aspects of the stack are managed together, allowing MongoDB to perform a variety of checks to ensure the test does not result in an impacting event. Within Ops Manager we are unable to offer a similar level of insurance and so will not release this feature to Ops Manager. However, we have seen our users implement their own test failover scenarios using their own testing infrastructure and tools, including Ops Manager as a part of that stack, to perform the orchestration required for controlled testing.
-
1 vote
An error occurred while saving the comment Thank you for the feedback Jonas. Sent you a direct message for more information on the specific tools you use but feel free to post here as well.
-
20 votes
An error occurred while saving the comment Hi Gergely, Thank you for the feedback. I'll move this to the backup section for Atlas as we'd need that as a feature first before we could support in Terraform. Moving there will allow it to be more easily seen by the right people here. Thanks! Melissa
-
8 votes
An error occurred while saving the comment Hi Sadok, Thank you for the submission. We've intentionally not included this feature in our provider as state management of a temporary resource can prove problematic in Terraform. We have, however, created a secret engine for managing Atlas database users with HashiCorp vault (included in the Vault binary) that allows for programmatic management of users with a lease that many find inline with their security requirements. Thank you, Melissa
-
65 votes
An error occurred while saving the comment Hi Ravindra and other here, Currently the Atlas API focuses on administration functions and the authentication to that is via a programmatic key that does not have access to the data layer, since our Terraform provider covers this API it is providing functions inline with the capabilities of the API. However, it would be great to know more around use cases that are driving this request. If you'd like to share/discuss it would be great to talk. Feel free to reply here or reach out to me directly, melissa.plunkett@mongodb.com. -Melissa
-
1 vote
An error occurred while saving the comment We released support for third party integrations today. However we cannot support OAuth2 in Terraform until our API supports it. I will move this request to the Monitoring and Metrics teams forum, which will help surface it to the correct team. Thanks for the submission!
-
1 vote
An error occurred while saving the comment Hi Edward - Glad to hear you love MongoDB, that's great! It would be great to know more about your use case that requires both eu-west-2 and programmatic user of M0s, our free tier in Atlas. Would you be open to speaking directly or sharing more here?
Also, I'm going to move this request to our main Atlas forum here as Terraform supports what is available via the Atlas API. Currently M0 creation is not supported by the API so not supported by Terraform.
Thanks!
-
9 votes
An error occurred while saving the comment Hi Samuel. Thank you for the feedback. Let me look into this and see what happened in the support case so I can provide a response. If you'd like to reach out directly in the mean time my direct contact is melissa.plunkett@mongodb.com.
-
6 votes
We are going to expose this via mongocli first as it would probably makes a fastest solution.
AdminMelissa
(Lead Product Manager, MongoDB)
shared this idea
·
Thank you Suresh for the feedback. As you note, the best way to schedule pausing like this within Atlas is to use Atlas Triggers. You can set it to make the API call to pause/unpause. Have you tried setting up the trigger with Terraform to make it easier?