Atlas App Services
238 results found
-
Expose secrets as value more easily
Having many secrets and exposing each of them as a value can make the list in the values section of Atlas App Services a little overwhelming. This is unnecessary as most of the time, the name of the exposed value and the corresponding secret are the same.
My suggestion: Make an option when adding secrets to automatically expose this secret as a value of the same name. This could be a checkbox when adding a secret in the UI. Then, in the list of values / secrets. Don't show them twice like now but maybe add a tag on each…
3 votes -
Autocomplete references for Functions, value and environment variables
It would be tremendously helpful if while referencing a function or a value or an environment variable - the IDE will autocomplete the possible options, for better efficiency and mistakes reduction. Going back and forth around the UI or trying to remember by heart is error prone, and copy-pasting is valid only for a single action at a time.
3 votes -
Flag to deploy individual functions
Run into many issues where devs deploy over one another. I understand that building the functionality to test realm functions locally could take a while to set up. However, deploying individual functions using a -f flag in the push scripts would be an alternative solution!
3 votes -
Expansion of user permissions
Currently we have developers test code in the realm ui if multiple people are needing to work on the backend as there is no current method to deploy locally (ideally how you can with AWS Lambda). As of now, you can only directly modify a realm function in the ui if you have "Owner" permissions. This is very scary to give to individual resources
3 votes -
Add Trigger call for failed/unsuccessful login
We can have a trigger that fires based on a wrong password. For examples, as an user If I enter wrong password then it should be handled using some trigger.
I have already opened a case on mongodb support :
3 votes -
Headless Browser (Puppeteer)
Most things that you can do manually in the browser can be done using Puppeteer!
Some examples:
Generate screenshots and PDFs of pages.
Crawl a SPA (Single-Page Application) and generate pre-rendered content
Automate form submission, UI testing, keyboard input, etc.3 votes -
data api logs needs more details: origin, raw data in payload, etc
the data api logs are pretty useless, they need to contain the complete metadata from the api call. source ip address, headers, request body payload, etc...
3 votes -
easily manage single configuration file for different environments for ci/cd
simply support environment variables expansion in database name or table name
this way a single configuration folder can be used to configure multiple realm apps
but each realm app will use a different database/table so the data is separated.
an official mongodb example code from a blog post about this topic uses this expansion but talking with support they said it is not supported and that the example code is wrong.3 votes -
Programmatic Support for Uploading Dependencies
Right now the Realm Administration APIs [1] only let's users list dependencies. It would be helpful to have an endpoint to upload dependencies as we have 8 env and uploading manually to all envs is painful.
[1] https://docs.mongodb.com/realm/admin/api/v3/#dependency-apis
3 votes -
View cloud data in Realm Studio mongodb
Realm Studio is helpful to explore data from Legacy Realm Cloud. But Realm Studio mongodb does not support opening 'Realm Cloud'.
Please consider this feature.
Thanks so much,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 -
Improve Realm Web RBAC Granularity
Currently, You need to be a "Project Owner" to view GraphQL configurations in Realm Web. I also need "Project Owner" to execute a schema validation. I would like to see more granular access controls for Realm Web similar to the granularity of MongoDB Atlas.
3 votes -
Support for user "Presence"
At this point in time, it is not possible to determine in Realm Cloud whether a user is connected to a MongoDB Realm app and is online or not. In other words, there is no built in mechanism in Realm for figuring this out. Firebase has had this feature for years, so I think it only nature that Realm should as well. This is absolutely critical for developing something like a chat application.
3 votes -
Complex Realm Querying (No Partitions)
So there's currently an issue with Partitions where if you have multiple complex relationships, files that need to be in multiple partitions aren't accessible.
Let's say you have a User Object and a Tribe Object.
Each user has a list of tribes they are in, and each tribe has a list of users they are in.If you partition for each User, and User 1 and User 2 share a tribe, the User 2 partition will be unable to access the tribe.
If you partition for Tribes, and Tribe 1 and Tribe 2 that share a User, one partition will…
3 votes -
Add the ability to use a value to reference a database in a trigger
It would be great if we could use values for the database reference in a trigger, instead of having to select a database from a drop-down.
An actual use case:
To be able to use Realm for our various staging areas, we have created multiple Realm apps. One for production, one for UAT, one for test, etc. Each of them pointing to the databases for their respective staging environment.
We are using Github deployments, and we use a separate branch for each of the staging environments. So when something gets committed to the "deploy-test" branch, it gets to be deployed…
3 votes -
Expose dbstats / stats in Functions
Add to the allowable MongoDB actions to be able query the database size, like: db.runCommand({ dbStats: 1, scale: 1 }) or by collection like db.sources.stats()
3 votes -
Automatic created_at and updated_at Fields
Would be nice to have this feature as a checkbox on each collection or default for the entire database and it should be in utc or a checkbox for utc.
3 votes -
Accept New Release of MongoDB Realm
We need the ability to be able to accept new releases, similarly to how you push updates to clusters so we can 1)be aware and test new releases in test environments 2)schedule updates for least disruptive periods.
3 votes -
Search Across Functions Code in Cloud UI
In writing any app, there are likely to be multiple Functions stored. A developer should have the ability to search for specific snippets or text elements across all Functions.
3 votes -
Ability to set parameters through a webhook path
It would be nice to use webhook path to pass payload to the webhook for example:
/api/mypath/{deviceId}/dataInstead of
/api/mypath/data?deviceId={deviceId}3 votes
- Don't see your idea?