Atlas App Services
248 results found
-
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
12 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?