Atlas App Services
248 results found
-
1 vote
-
Support of dependencies which rely on an extra binary
We would like to establish connection to OracleDB from a REAM Function. For that we're using
oracledbnpm module.However this module is dependent on a third party binary (Oracle Instant Client “Basic” or “Basic Light” package), which should be in the PATH and located by the npm module.
Can REALM add support of this feature?
3 votes -
changeEvent cluster name
I want to be able to programmatically access the clusterName from change event or global variable for example:
changeEvent.ns.cluster = <CLUSTER/SERVICE name>
global.CLUSTER_NAMEI need this when I want to perform an update on same collection/document after the trigger, but i don't want to hardcode the clusterName - because i have multiple environments - each has its own cluster (dev/sandbox/prod etc...)
1 vote -
One-time scheduled triggers
At the moment, MongoDb offers the ability to schedule triggers periodically using Cron Jobs. It would be really handy if a user could schedule a trigger to run only once and execute a function as my use-case requires.
1 vote -
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.
-
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.
12 votes -
Containerized Functions + Logging + Dependencies Improvements
I believe most of the below asks would be resolved if you allowed containerized functions to be uploaded and we can have the correct execution environment.
Allow larger function sizes
Allow more larger dependency sizes
Allow 256kb size per log entry
Allow Unlimited log entries per function execution
Output formatted logs, don't want to scroll right forever
Add refresh button for logs
Log arguments for triggered function automatically
Don't truncate logs
Allow logs to be streamed so that you don't need to refresh logs
Increase execution time to 15-30 minutes
Allow dependencies to be imported outside of function definition
Allow…1 vote -
GitHub Deploy - pulling deletes standard files, like LICENSE, README.md, etc.
If I make a change in the UI, deploy, then do a git pull on my local machine, the pull deletes my License, README.md, and .gitignore files. These are standard files and should not be changed on pull. It's like it's overwriting everything from scratch instead of just doing a diff. My repo is public and I need to include this basic info.
1 vote -
Allow for Name filtering in REALM logs
Currently Realm logs are pretty limited in functionality. It is hard to sort, filter and track down a specific log file. A filter option based on name would be beneficial. The filter could show all of the recent runs of something based on the name. Also, it would be nice to see the log pages refresh automatically.
4 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).
30 votes -
More Mongo DB actions parity with the Node driver
The actions available via https://docs.mongodb.com/realm/mongodb/actions/ do not match the API exposed by the Node driver.
For example, the https://mongodb.github.io/node-mongodb-native/4.0/classes/collection.html#createindex function would be extremely useful for our use case, I can't see any method for programmatically creating indexes via Realm.
For example, the https://mongodb.github.io/node-mongodb-native/4.0/classes/collection.html#bulkwrite function returns a completely different type from https://docs.mongodb.com/realm/mongodb/actions/collection.bulkWrite/, making unit testing our realm functions locally extremely difficult.
I'm unsure what reasons there are for this disparity (especially when I can use the mongo node driver to connect locally to an Atlas cluster, but I can't use any of these methods in our deployed application in Realm).
1 vote -
Support for JSON schema oneOf / anyOf / allOf
In our current project we have the requirement to support slightly differently shaped documents, contained within in the same collection, that are identified by an enumerated "type" field. In order to do this we require the ability to make use of the oneOf / anyOf / allOf polymorphic features of the JSON schema which would then ideally be relflected in the MongoDB Realm GraphQL endpoint. I was informed that this was being looked at a while ago but can see no associated feature request.
2 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.2 votes -
Retain GraphQL Query History
The GraphQL feature has a history list while you stay on the page. It would be a great improvement if it maintained that history even if you navigated away and came back.
2 votes -
Realm update/replace logs
I think an enhancement to the realm logs that explains the deltas (what has changed) on a given document for updates/replace would be extremely useful.
At the moment we receive an ID and the type of change that has happened which is fine for an insert/delete.
But to understand what has changed on the document for an update/replace would help a lot in diagnosing any issues we have seen with realm in the past.
1 vote -
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
AdminOtso
(Admin, MongoDB)
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
-
views
Use views (not materialized) as source for realm sync (potentially as read only)
2 votes -
Array types in generated GraphQL schema should follow JSON schema of a collection or custom type
Hello!
Realm generates GraphQL schema that does not reflect the exact JSON schema of a collection or custom type when it comes to array fields. Generated GraphQL schema allow arrays to contain NULLs even if this is not stated in JSON schema.
For example, please see collection schema in the attachment. (Not able to insert JSON here in a readable manner)
For this schema, I expect Realm to generate following GraphQL type for my collection:
type MyCollection {
_id: ObjectId!
arrField: [String!]!
}
Please note the exclamation sign inside the square brackets. This states that the array item can only…6 votes -
logs
When filtering logs I should be able to enter a date/time in the near future for the To date in order to produce a shareable URL in the address bar that will include log lines in the range from some specified date in the past until "now" without having to precisely enter what "now" is.
2 votes -
Retry function
We use Realm functions to update related documents in our Mongo Atlas cluster. Sometimes, the DB connection (via
context.services.get("mongodb-atlas")) fails. We should... be able to retry establishing a connection? (Or even easier, just configure a retry for the Realm Function itself.)2 votes
- Don't see your idea?