Atlas App Services
240 results found
-
Better management of outgoing IP addresses
MongoDB publishes the list of outgoing IPs, but it is very long and there are no ranges, just dozens of random IP addresses.
It would be nice to have better options to manage this. Perhaps a paid option for narrower or custom IP ranges. Notifications when the approved IP list changes in any way?
1 vote -
Validate permissions when saved
When changing permissions in the UI, there is no validation if the code being entered is valid. This leads to hard-to-debug runtime errors.
I.e. It is possible to enter something like this:
{ "foo": "bar" }With no kind of warning.
2 votes -
Account Level Functions, Triggers and Values
Can you please add the option to mark a 'Function, 'Trigger' and 'Values' to be available beyond a Realm App?
That is, global type option for a Cluster and Account. This way we do not have to keep redundant copies. This is important for multiple Realm Apps, development & testing, etc.
Thank You!
4 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
2 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).
31 votes -
Need more close realm server in Asia
currently realm server which can use in Asia is too far and limited like below link
https://docs.mongodb.com/realm/admin/deployment-models-and-regions/#cloud-deployment-regions
so, i think it has some delay to request realm server as well as management using realm web UI
it would be nice to be able to use more close server19 votesWe have started work on more regions as well as cloud providers.
-
Allow to create and store templates for Realm's 'Sync Permissions'
Please allow to create, store and use custom templates for 'Permissions' for a partition-based 'Sync Permission' setup. This is under the area named "Define Permissions". There are pre-built ones but no custom ones. Makes you have to keep adding in each time you make changes.
2 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 -
On 1st Data API documentation page, add a list of lacking mongodb features
Starting a project with Data API and discovering later in the project there is missing some required mongodb is horrible. I suggest to add a big warning on the 1st page of documentation of Data API with all missing mongodb features, to help to decide if Data API is a good fit for the user.
1 vote -
Failover Support
Per Support, Triggers may not process if the App Services app's deployment region is experiencing wide-scale issues. Currently triggers will execute in the single region of their deployment.
For multi-region clusters, triggers should be able to failover to another region and continue processing.
1 vote -
Terraform Provider
It would be nice to be able to managed Realm Applications via Terraform, similar to how MongoDB Atlas can currently be managed via the mongodb_atlas from Terraform provider.
13 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 -
Sync Permission at Object / Document Level
Please allow Read & Write Sync Permissions to be per object (aka: Document) being processed, rather than at partition-level. Thereby allowing to use '%%root' as a Function's parameter to access the Document to allow permission for read or write per request. Also the permission would carry (deep) through for nested / embedded objects & List<>s. Further, please expose (if not available via '%%root') the Schema (at minimum the "title" property to access Object type).
2 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...
2 votes -
Add App Services Github Integration support for self-hosted Github Enterprise Server instances
Right now there is no way to integrate App Services with Github if you're self-hosting your own Github Enterprise instance and you are required to create a Github Cloud account to do so. Please add App Services integration support for self-hosted Github instances.
1 vote -
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…
32 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 -
Change message "not master" to something more meaningful
Sorry if this is the wrong category but I assume that the nodejs component that is trying to write to MongoDB/Atlas is doing so via the Data API.
Once in a while, in association with an attempted insert, I see the error message "not master", which is not giving me a clue about what's really happening. When I look through my logs, I see this message periodically in batches that occur within a few seconds. I had to reach out to support to find out what was happening. It turns out, it's just the server applying a software update.
Is…
1 vote -
Support array-like ($in, $all, etc) queries in Data API
Similar to the find() method, the Data API could support multiple (array-like) structures while querying, ex:
{
dataSource: 'cluster',
database: 'database',
collection: 'collection',
filter: { property: { $oid: { $in: [ObjectIDs] } } }
}directly analogous to: data.getCollection('collection').find({ property: { $in: [ObjectIDs] } })
3 votes -
1 vote
- Don't see your idea?