Atlas App Services
240 results found
-
More Intuitive GUI for Relationship Modeling
I know "Add Relationship" button works very well. However, you can check some of Headless CMS out there and learn from how they are letting users to handle relationship modeling.
I think the one from Strapi is the best. It's like attached image.
You can search on google image by "Strapi relation" and find more images.8 votes -
Disable Sync
A flag to enable/disable cloud sync on Fully-synchronized realms.
This would be convenient if you're offering sync as a premium feature.
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 -
function sandbox
It would be great to have a function sandbox area, where you can write and called previously used functions (saved like notepad++ does) without having to create the function and commit it.
This would be for trying thing out or performing quick tasks for which you don't want to go through all the hassle of formally creating a function.
8 votes -
Allow manually disabled trigger to resume without resume token
I am filing a feature request for the option to: Disable a trigger manually and be able to restart it without using a resume token (i.e. such that DB events that occurred while it was disabled will be ignored by the trigger, and it will simply start listening for new events upon restart).
8 votes -
Allow to pass user on Realm's Database Triggers
Currently I can create a Database Trigger, that when calling its Function I can restrict based on "%%user" - through "Can Evaluate". Though since the Function is called by a Trigger and therefore runs as a "system user" I cannot access the User object (or its details) within the Function - I (personally) mainly want the userID & email - though whole object would be better.
Since a Function is called by a Trigger and therefore it runs as "System User" - Please allows us to pass an array of arguments for the Function. This could be a field after…
7 votes -
Realm Trigger Event Projection should support exclusion
Realm triggers with a projections must include "operationType": 1. This makes excluding fields impossible because, according to the documentation:
if you exclude fields, you cannot also specify the inclusion of fields
The only work around we have found is to list every single field in the database and this would require an update anytime we add another field to the model. This is quite cumbersome and should be easily resolved with a simple exclusion.
7 votes -
Application Deployment in GCP
Currently deployent is only available to AWS but Atlas allows deployment in GCP.
We need to have deployment close to GCP for better performance consideration.7 votes -
Atlas App Services regions in the UK
UK Data Protection requirements often require data to reside within the UK, something that cannot be supported through Atlas App Services today.
For all features (especially Charts, Realm and Triggers), being able to select the UK as a region would unlock additional customer use cases.
Given I am a UK domiciled MongoDB Atlas user
When I use MongoDB Charts
Then all traffic should remain within the UKGiven I am a UK domiciled MongoDB Atlas user
When I use MongoDB Atlas Triggers
Then I should have the option for my trigger to invoke from a UK data centerGiven I…
6 votes -
Client Side Field-level encryption for Realm Sync
Support client-side field-level encryption in MongoDB Realm.
https://docs.mongodb.com/manual/core/security-client-side-encryption/
https://docs.mongodb.com/manual/core/security-automatic-client-side-encryption/Basically, it would be nice if we could mark fields as being "sensitive" in the schemas, and Realm Sync would make sure to encrypt the fields before they are sent from the client app to the MongoDB Atlas database.
6 votes
Otso
responded
Here's an example on client side encryption with Realm Kotlin SDK on Android https://github.com/realm/realm-kotlin-samples/tree/main/AppServicesUsageSamples/apps/property-encryption
-
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 -
Google Pubsub Client Support
support Google Pubsub Client API's in functions
6 votes -
Copy functions from one cluster to another
It would be great if you could copy a Realm Service or Function from one cluster to another. I find myself having to open two tabs and coping the function code then checking all settings are the same etc.
We would normally dev on a "test" cluster then copy Service functions over to "prod" cluster. Or am I missing something?6 votes -
Allowed Request Origins should support URLs with wildcard characters
The Allowed Request Origins list in the App Settings, at this time, doesn't support URLs with wildcard characters. As modern services like Vercel generate dynamically new URLs during development, the list needs to be updated every time with the current URL, while having an option available that would accept "https://*-myappname.vercel.app/" would simplify that step.
5 votes -
Trigger event queue metrics
We recently ran into the problem that our trigger was suspended because the resume token was no longer present in the oplog.
The problem was a combination of queued up trigger events and a short oplog window and the suggested solution was to increase the triggers performance by parallelizing it and by increasing the oplog size to get a bigger oplog window.Unfortunately, we're not able to verify the real success of these suggestions, because even though we can monitor the oplog window in the metrics, there are no metrics for the trigger queue itself. As a result, we can't…
5 votes -
Add support for GitLab
As an alternative to using GitHub
5 votes -
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…
5 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.
-
nodemailer Support
Nodemailer is currently not supported because of the punycode dependency. Would be nice to send mails directly on the mongodb server.
5 votes -
Passwordless authentication provider
Passwordless logins are quite commons nowadays. Firebase supports "Login with email link" (https://firebase.google.com/docs/auth/web/email-link-auth). Would be nice to have the same in Realm.
5 votes -
Schema for Realm's JSON Files to Enable Auto-Completion
This is a minor suggestion but it will be great if intellisense works for Realm-specific json files (i.e. "auth_providers/api-key.json", "services/mongodb-atlas/rules/db.collection.json", etc).
It will be helpful for developers using the Ream's "Deploy with CLI/GitHub" feature (which is great). I guess it may help reduce confusions; for example ObjectId/ObjectID/objectId.
VSCode has built-in support for JSON schema, and it seems additional schemas can be specified via three options: $schema in the file, VSCode settings or an extension.
https://code.visualstudio.com/Docs/languages/json#_json-schemas-and-settings5 votes
- Don't see your idea?