Realm
- or
- ~ No ideas found ~
-
on premise solution
Allow MongoDB to be used for on-premise solutions to offer early on integration or govcloud support for Realm.
18 votes -
Allow deeper relationships under Rules
I really like being able to use GraphQL and how you can auto generate a schema but when trying to relate fields I noticed it would only let me relate top level fields.
For example - we have "accounts" and "users" under accounts with user Id on a related object. But I cannot do related userId back to account.user.userid since user is an object. I was hoping after I generated a schema for all the collection I would be able to drill down deeper but no such luck.
17 votes -
Actual API Documentation
There is various documentation for the many Realm/Stitch SDKs but almost no information about the underlying API endpoints, this needs to change and we need some detailed docs for working with the API itself.
I am trying to get an app running with the GraphQL API but have found working with the authentication APIs to handle auth tokens and sessions to be a bit of a nightmare. This page https://docs.mongodb.com/realm/graphql/authenticate/ has some useful information but doesn't even give the endpoints for logging out or explain how to properly handle the email sign up process using API endpoints in place of the SDK. This is particularly important when working in an isomorphic environment like NextJS, which is perfectly doable with plain APIs but currently impossible with the current Node/Browser SDKs.
There is various documentation for the many Realm/Stitch SDKs but almost no information about the underlying API endpoints, this needs to change and we need some detailed docs for working with the API itself.
I am trying to get an app running with the GraphQL API but have found working with the authentication APIs to handle auth tokens and sessions to be a bit of a nightmare. This page https://docs.mongodb.com/realm/graphql/authenticate/ has some useful information but doesn't even give the endpoints for logging out or explain how to properly handle the email sign up process using API endpoints in place of…
16 votes -
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 -
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 -
External Dependencies Management (npm)
A lot of 3rd party libraries don't work, even ubiquitous ones like Joi. We upload zipped node_modules and all we get are errors.
Devs now spend time building simplified versions of these libraries so we don't get the full benefit of a using a battle-tested library and also waste time writing functions that we shouldn't need to write. This is a huge pain and a productivity killer.
14 votes -
Use node modules in Functions
As far as I understand currently it is not possible to use node/npm modules is Functions. Would be great to have it.
14 votes -
Cascading Deletes
Please add support for cascading deletes.
Related GitHub Issues:
https://github.com/realm/realm-core/issues/746
https://github.com/realm/realm-java/issues/1104
https://github.com/realm/realm-cocoa/issues/118614 votes -
Custom GraphQL Schema for MongoDB Realm
Dear MongoDb GraphQl Stitch developers,
Is it possible to add an ability to modify the final GraphQl schema (in order to remove unnecessary for my API stuff)
OR
Build it based on existed roles?For example, Im building a "read only" GraphQl API and have NO roles that can actually modify the data. So I find it illogically to have mutations in the Final GraphQl schema.
It would be great to have an ability to choose which exactly mutations/queries I need for my GraphQl.
Thank you.
14 votes -
Add retry policy to Atlas Trigger
A failed Atlas trigger gets suspended and will not retry without manual intervention. Some transient conditions can be retried and it would be useful to configure a retry policy with a trigger (at the Realm Function level). Retry X times with Y back-off seconds between retries, then fail (plus notification policy).
11 votes -
Add REST API Services
Add REST Services support analogous the GraphQL.
Some users on Realm desire a REST API to their clients as
oppose to a GraphQL API.Although this can somewhat be accomplished by adding a HTTP '3rd Party Service' and query the mongo collections, you don't get all Rules, Schema, and other useful tools and services which are provided with the GraphQL option.
11 votes -
Option to have Realm app users in an Atlas collection
It would make a lot of sense to me if one could configure a Realm app to use a collection in the Atlas Cluster to store users instead of having a separate users database managed outside of Atlas, as the case is today.
To avoid a breaking change, this could be implemented as an option to how users are managed today.
This would solve most user-related feature requests and issues, as it would give the app developer full control of the user DB to do whatever queries or customization they want to. Maybe call the option "advanced" or such—more manual labor, more control, for those who want that. I'd even be fine if all auth methods except JWT were disabled when the "Store users in Atlas collection" option is enabled if that helps the implementation.
I get that if someone makes incompatible changes, it could break the auth and access system, but that almost goes without saying, and I think that would be an acceptable compromise.
In my use case, we have an app (https://bikerider.app/) running Atlas with a separate custom GraphQL node server, and I was looking at Realm Cloud to simplify our backend (e.g., the goal would be to replace our node servers with Realm Cloud). That said, we already have a user collection, so with how Realm Cloud is working, I am going to see if I can use our existing users' collection as "custom user data" and use JWT for auth since we already have a custom auth system. But there may be issues with IDs etc. Since we already have relationships between different users and other entities (ex cycling events) based on our existing user IDs and Realm Cloud will create new user IDs. Not 100% sure about this yet, I will need to explore more and see if it can be mapped somehow, but I believe it would help a lot if I could say which collection to use for Realm users.
Related to (would be solved as part of this feature):
https://feedback.mongodb.com/forums/923521-realm/suggestions/40550683-importing-users-in-bulk
https://feedback.mongodb.com/forums/923521-realm/suggestions/41390221-search-users-by-email
And so on.
https://feedback.mongodb.com/forums/923521-realm?category_id=388675&query=user
It would make a lot of sense to me if one could configure a Realm app to use a collection in the Atlas Cluster to store users instead of having a separate users database managed outside of Atlas, as the case is today.
To avoid a breaking change, this could be implemented as an option to how users are managed today.
This would solve most user-related feature requests and issues, as it would give the app developer full control of the user DB to do whatever queries or customization they want to. Maybe call the option "advanced" or such—more manual…
10 votes -
Deploy Application code from Bitbucket private repository
Currently it is only possible to link a Github account for deployment.
It would be great if we can use Bitbucket as well. I have my code in a private bitbucket repository and would love to have the ability to deploy from it.10 votes -
Add More Regions For Realm
Would be great if we can have more options for realm like south america and europe.
9 votes -
Terraform Provider
It would be nice to be able to managed Realm Applications via Terraform, similar to how MongoDB Atlas can currently be managed via the mongodb_atlas from Terraform provider.
8 votes -
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 -
Search Users by Email
In the users tab, I can only search by ID. If I don't have the users ID, it's nearly impossible for me to find a user in the list. Need to be able to search for a user by email ASAP. Thanks.
8 votes -
refresh logs button
Please add a refresh button to the Logs view. I realize a browser refresh does the trick, but a button above the Logs table is more convenient.
8 votes -
Documentation for Test (Jest)
There seems to be no documentation how to write good tests for realm at this moment.
8 votes -
MongoDB Realm vs Realm
Hi, I am an existing Realm/Realm Cloud user and am struggling to understand what the MongoDB Realm offering is and how it compares with the existing Realm/Realm Cloud solution.
Is there any documentation that explains what the difference is between the two solutions and what if any migration is required.
It's not clear whether the latest cocoa Realm database v5.1.0 is still compatible with Realm Cloud nor is it clear whether there is any plan to continue supporting the current Realm Cloud solution. A nice clear description would be much appreciated.
Regards
Duncan8 votes
- Don't see your idea?