Atlas App Services
258 results found
-
163 votes
Please send any feedback to kaylee.won@mongodb.com going forward – this feature is under review, so we would love to hear from you. Thanks!
-
Local development tooling
Similar to AWS SAM (https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-invoke.html) or Google Cloud Functions Framework (https://cloud.google.com/functions/docs/functions-framework).
I.e. the ability to run functions locally. It's expensive and slow to have to run and test code in a project remotely all the time even for small changes.
152 votes -
Support TypeScript
I know this is probably a very complex feature, but I'd like to work with TypeScript when writing functions.
Some stretch goals:
- full integration with VSCode so we no longer have to use the web editor
- add support for testing functions (through CI/CD)101 votes -
Pagination in GraphQL
We have slicing via limit: INT, but we do not have the ability to specify an offset. Are there plans to add this soon?
GraphQL Documentation actually specifies their pagination terms as follows:
first: int
offset: int
after: _id
Are there plans to implement this at all?88 votes -
Upgrade Node.js version (from v10 to v14/v16)
It would be great if you can upgrade the version of Node.js used in Realm Functions (currently in version 10.18.1). Version 10.x, which was an LTS, has been unmaintained for many years. The end of life of Node v12 is scheduled for April 2022.
Is it possible to upgrade Node to version 14 (at least)? Another feature would be to let us choose the Node.js runtime version directly from Realm UI or the CLI (it's possible for example with AWS Lambda).
Working with Node v10 is really difficult for us since most of the dependencies are not compatible with it.
…
57 votes -
Configure rate limit
It would be nice to be able to configure rate-limiting to prevent DDoS, scraping or unwanted requests that could highly increase the cost of MongoDB Realms
55 votes -
Ability to change/update email address of Application User
Users should have the ability to change their email address.
Applications cannot give the ability to users to change their own email address. Once a user is registered/created there is no way for such user to update/change their own email address.55 votes -
Increase of Functions timeout
Timeout is set to 90 seconds. This value is a fixed setting and is too low for extensive ingestion functions.
A default value of 600 seconds would be helpful.
Even better would be the ability to set an individual timeout value per application in the settings.
47 votes -
Dark Mode
Support a "Dark Mode" for the MongoDB Realm UI.
39 votes -
Folders for Functions, Values
Add folders to the Functions and Values areas and then to make it 10x better by adding permissioning by folder so we can keep our clients from altering sensitive functions/values in specific folders.
38 votes -
Adding or removing elements from array fields
It would be helpful to support array add/remove in update mutations. I've been running into this most often when dealing with one-to-many relationships.
For example, adding/removing books from an author. Currently, you would have to fetch the entire array of books to add or remove the book linked to the author. If I could supply the foreign key to add/remove from the relationship that would be fantastic.
36 votes -
Filter logs by Function name
Logs can only be filtered by type, user and timestamps. Would be very useful to filter by function name
36 votes -
More flexible Custom User Data / User Linking
On Stitch, you can have multiple providers for identity, but then it creates multiple users even with the same email address if you have someone from say Google or then someone who authenticated via email. There is a way to merge two accounts, but it requires the user to authenticate twice and that's not an ideal user experience. One solve is to treat them as one user. The other solve is to create a user metadata collection which both identities can reference, but if you're trying to add rules and permissions you can't put an array of options in the…
36 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.
34 votes -
on premise solution
Allow MongoDB to be used for on-premise solutions to offer early on integration or govcloud support for Realm.
34 votes -
Automatically Refresh Auth Tokens on User's Custom Data Change
Currently, getting updates to custom user data on the frontend requires periodically refreshing the token. A potential improvement would be for MongoDB Realm/SDKs to detect these changes automatically and streamline the token refresh so application code wasn't required to handle this case.
34 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).
30 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…
30 votes -
python
Python support would be great to allow us to have a single code base
30 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.
24 votes
- Don't see your idea?