Atlas App Services
237 results found
-
RDBMS Connectors
Make the previously available data connectors available for Realm’s data adapter to sync data from the Realm Object Server to a Microsoft SQL Server and vice versa.
1 vote -
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.
2 votes -
Enable Function Testing (TDD/CI/CD)
It will be great if Tests could be defined within the UI.
For example having the option to write a jest test that is executed before deploying any changes to the Hosted app would be awesome.
4 votes -
Availability of Args in Function Context
Not sure if this is do-able already or not. Couldn't find documentation.
I have a function that looks like
exports = function(dbName, collectionName, pipeline){...
I want to be able to access the arguments sent to the function in the Can Evaluate JSON expression.
I assumed it might work like
{
"%%args.dbName": "eflex-test"
}but that doesn't seem to work
1 vote -
Filter logs by Function name
Logs can only be filtered by type, user and timestamps. Would be very useful to filter by function name
37 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 -
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.
2 votes -
Logging Enhancements
We need the following enhancements
1. Need more than 80 characters
2. Need ability to turn it on and off by level (Log4J)
3. Need ability to turn to higher level of logging on a single call10 votes -
Broader Push Notification Support
I've moved from Firebase because of the lack of support for React-Native and I've just discovered that I need to use Firebase to receive Push Notifications from my App. I'm aware of the complexity of adding this layer to SDKs, but you're already much ahead of Firebase in terms of SDK maintenance and support, being able to make a full app's stack would be wonderful for many, I think.
1 vote -
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.
18 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}2 votes -
Ability to expose API via our own custom DNS entry
We would like to expose the APIs created directly to our clients. But we would like them to utilize a domain from our company. At this time we are going to use AWS API Gateway as a reverse proxy.
But all we really would need is the ability to host our ssl cert that corresponds to our domain
14 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 -
Ability to set Values in Functions
Ability from webhooks and functions to call context.values.set() and set a value that can then be referenced somewhere later. This could dramatically cut back on calls to outside APIs as we need data in multiple places so we end up having to make several calls.
5 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.
2 votes -
Support for Twitter Authentication
Currently, you only support Google and Facebook for social logins. Can Twitter also be added?
3 votes -
Human readable URLs in UI
Currently, the app urls are extremely long and unreadable, for example: https://realm.mongodb.com/groups/5ab028594e6581148629dc65/apps/5b28f4615fdce07a74cd7f50/triggers/5bcf226fe707c05350750dcc
This looks pretty ugly. It would be a lot more user friendly to:
- eliminate the /groups/<groupID>/ portion of the URL entirely - the app ID already uniquely identifies the group anyway
- use the clientAppID instead of the raw objectID for /apps/<appID>.
For example, the above URL could instead be represented as
https://realm.mongodb.com/apps/my-app-xyz/triggers/5bcf226fe707c05350750dcc
with no loss of functionality or precision0 votes
- Don't see your idea?