Realm
-
Option to save Realm Logs to a collection
Currently logs in a Realm app are viewable via the UI or via the API.
The API limits return results to a maximum at 100 a time.
I would like to be able to save logs (errors, especially) into a collection so that I can query or analyze them how I see fit.The current work-around is ensuring that each of my functions has an appropriate try/catch/log, effectively replicating the logging Realm already does. Put another way, please expose the logs in a way that we can truly query them.
3 votes -
Allow user-set 'deployment id/name' via realm-cli
We're using github actions to fully automate our realm deployments with the cli, and I'd like to be able to give a user-friendly name so that we can easily identify the currently deployed version (such as the git hash). Currently under "deployments" what I see looks like an internal realm deployment id.
1 vote -
Injection Attack Documentation
Hi MongoDB, we are in the process of preparing for production and while we have found some susceptibilities to injection attacks on mongodb (see OWASP Top 10) there does not seem to be any documentation explaining all the potential known avenues of attack for MongoDB. The response from the engineering team is there is shared responsibility, however, how can we share responsibility for what we do not know? We as engineers rely on the product owners to give known attack vectors so that we can share that responsibility.
That said, there are two we know about, escape for the $…
1 vote -
Please write explicit rules for anonymous auth users deletion or provide controls to adjust the behavior
In the documentation for anonymous auth, it says that Realm may delete anonymous users that are 90 days old https://docs.mongodb.com/realm/authentication/anonymous/
There is also a mention about 30 days of inactivity https://developer.mongodb.com/community/forums/t/persisting-anonymous-users/10247/2?u=anton_p
That's hard to rely on something so broad to make decisions in the app logic. Is it possible to clarify this behavior or provide control over this flow?
4 votes -
Return the Webhook URL through the CLI
When creating a service Webhook through the CLI, return the Webhook URL through the CLI instead of requiring users to get it from the UI.
1 vote -
Increase RealmReturn Body Max Size
The maximum return body size of a realm webhook is 4MiB (4194304 bytes). That might seem enough for most applications but when dealing with massive amounts of data, e.g. timeseries data over years, that is a hard limitation.
It requires the client to make many more requests that would be necessary.In our special case we want to return one whole year worth of data per request to make things easier for our clients (currently they can get 3 months).
Given a 16MB Limit on a MongoDB Collection Document, this would seem like a sensable option for a limit if…
3 votesHi Marc – We have a ticket for this that’s near the top of the backlog and plan to increase the limit to 16MB in the near future.
-
Set custom endpoint for s3 service
Allow users to use a custom s3 endpoint for example: nyc3.digitaloceanspaces.com
1 vote -
Export/import users in Realm app
Option to export all Realm app users and import them.
It's a major concern that users can't be exported. Both for backup reasons and also for moving them between apps.
If you delete or loose a Realm app you are out of business because the users are gone and if you mistakenly chose the wrong deployment region, you can't move the app because you can't move the users.
I think this is absolutely critical to growing a business using Realm apps.
14 votes -
Custom OAuth 2 Providers
Allow us to input custom oauth2 providers for login. I know we can do something similar through custom functions, however, it would be nice if we can just add them easier.
1 vote -
Expose default confirmFn for use within custom confirmFn
In my application I have implemented a custom confirm function which blocks registrations unless they have an email address in my company's domain. When this is the case, I would like to send the signup email as usual. However there isn't a way of doing this so in order to implement this basic filter I have to setup a 3rd party email service.
It would be good to allow calling the default confirmFn from within the custom one
1 vote -
1 vote
-
Prevent App - Cluster Deletion
We have Realm applications running in Dev, Staging, Production.
Someone accidentally deleted the Staging application. (It's easy to do it)
Hopefully, it wasn't a production one.
Please add a way to lock or prevent Application and Cluster deletion.
That way, we add an additional step which is a password, for example, and prevent accidents to happen.
Thanks!1 vote -
UI update when adding user/pass auth before deploying sync the 1st time
UI update that lets you know the reason you can't add user/pass auth until initial realm sync is deployed.
1 vote -
More Granular Realm UI Permissions
At this time, the only permission that allows access to Realm is Project Owner; however, Project Owner grants permission to change a plethora of things inside Realm. In our case, we have testers who do not need the ability to change code. The testers only need to change Values and add users. Could a new permission class be created to support this?
14 votes -
Ways to pause a Realm App
It would be awesome, if there was a way pause a Realm App via functions.
Currently we are pausing our cluster every night using a trigger. However that causes all our Realm apps' sync and triggers to crash, so I have to manually restart each of them every morning.
It would be awesome if I could pause/unpause a Realm App from a function. Something like this, maybe:
context.realm.app([app-id]).pause()
context.realm.app([app-id]).unpause()1 vote -
Realm roles in Atlas Projects
Currently we only have two roles available for Realm Users:
1. Project Owner
2. Project ReadOnly
Would be great to have more roles for Realm Users with the ability to give access to specific Realm App or give access to Realm only without giving access to the entire project. Something like Realm WriteRead and Realm ReadOnly roles
Thank you,
Anton8 votes -
Support of multiple partition keys
You could actually increase the awesomeness of MongoRealm, when you support multiple partition keys on one object.
Example:
We have a collection of customers in MongoDB, our App is showing the customer information to the users, but only for those users, that are "allowed" to see the customers. So the customer object has a partition key holding the userName it is assigned to:customer { _id: "12345", partition: "bob", name: "MongoDB Inc."}
customer { _id: "12346", partition: "alice", name: "Microsoft"}now we want, that alice also sees the customer "MongoDB Inc." in the App.
The solution could look something like…
6 votes -
GraphQL in Realm Functions
It would be useful to have an integrated GraphQL client that is authenticated against the cluster available in Realm functions, to create stored queries and modify these in postprocessing in a Realm function.
3 votes -
Re-Add support for querying LinkingObjects with GraphQL
In RealmSwift, one can define LinkingObjects to refer to inverse M2O or M2M relationships. These are not supported by queries in MongoDB requiring to create custom resolvers. It would be very useful if these would be accessible in GraphQL.
3 votes -
user object documentation
The documentation for user object (as many other parts) seems incomplete and doesn't provide enough information about the possible responses you can get from the API and the SDK.
https://docs.mongodb.com/realm/authentication/user-objects
Please provide documentation for the user object which includes the built-in authentication providers.
1 vote
- Don't see your idea?