Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
9 results found
-
Do not require Project Custom Resource for managing other Resources
We would like to adopt the Atlas Operator without managing our entire Atlas Project in Kubernetes, or we would like to manage the Project elsewhere, maybe in another namespace, in another k8s cluster or in Terraform.
It does not make sense that the
AtlasDatabaseUserrequires aAtlasProjectresource to exist. We want to manage users separately from the Project as those can be owned by different users in our system.Also the API and Terraform resources do not have this requirement so it breaks convention when the Atlas Operator has this unique requirement https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/database_user
To work around this we would…
1 vote -
Use kubernetes Atlas operator to create and manage only users
We are already managing the Atlas project using terraform and do not want to have two separate tools managing the same resource. We would still like to generate atlas users automatically through the operator. If there was a method of just providing the project ID as a string like we are able to in the terraform resource definition, this would not be a problem.
1 vote -
Enable setting encryption at rest details for project
Please allow us to set the encryption at rest KMS details for the project when we create the project
1 vote -
Add Atlas users to existing teams even though the Atlas user is still pending invite
Currently when we send invite emails for the organization we have to wait for the users to accept the invite before we are able to configure project level permissions. This often creates confusion and bad user experience; when users first sign in they are anticipating to see their projects but instead they see nothing until configuration is finalized.
Please make it possible to add users to teams which are still pending invite acceptance so the user experience is more seamless and less confusing.
7 votes -
snapshots without indexes
It would be great to have the option to save Atlas backup snapshots without indexes. When using TTL indexes, when the data is restored, it is automatically removed because it is expired. Being able to create snapshots without indexes would save a lot of time to the current workaround.
6 votes -
Kotlin support and Tutorials
Add Tutorials and Native support for Kotlin language. Preferable with ktor as the server
1 vote -
Enable Removal of a Subset Documents From Online Archive
Hi,
We'd like to have the ability to remove documents from an Online Archive. Mainly based on a date, but possibly other criteria.
Thanks!
37 votesWe’re currently researching the best way to add support for this.
-
Allow suggest password feature
In both mobile and desktop version of Chrome and Safari, there is a feature for automatically generating a strong password.
In the registration form for MongoDB Atlas, the password field in the registration form cannot take values entered this way. Please add this feature since password managers are in fact quite normal in this era.
1 vote -
Clarify Python vs PyMongo
When connecting to a Atlas cluster and selecting to connect via a Application you can select to connect with what "Driver" where you can select "Python".
For new users, they might think that the Python library (https://www.python.org/doc/versions/) is what is being referenced when in reality Atlas is referring to the PyMongo Driver.
For clarity, alter the UI from "Python" to "PyMongo" or "Python (PyMongo)" or something similar to differentiate between Python and PyMongo.
2 votes
- Don't see your idea?