Atlas App Services
234 results found
-
Improve Realm Documentation for Various SDK Integrations
With existing examples and documentation about Realm SDK integrations was a bit confusing.
Example: React Native SDK - hard to find best example for offline first mobile app with realm (sync)
if we can have GitHub repo example integrations with minimal features for each SDK implementation it would really helpful for the community to find what they're looking for.
Contribution: communicate can contribute by giving an example for each or multiple feature implementation examples.
3 votes -
Support parquetjs or parquetjs-lite dependencies
Our product would like to read the parquet file-format from an S3 source. Both parquetjs and parquetjs-lite are incompatible with Realm's dependency upload.
parquetjs: "boto" module is a duplicate of a top-level Realm default library.
https://www.npmjs.com/package/parquetjsparquetjs-lite: Parse error when uploading tarball. See screenshot below.
https://www.npmjs.com/package/parquetjs-liteThank you!
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 -
Allow modifying Sync permissions without having to terminate it. Maybe pause instead ?
Currently only way to modify/add permissions to Sync is at the beginning or terminating it. It would great if we could modify/add them with Sync Running or at least only pause it to avoid downtime and deleting cache from sync.
3 votes -
Github Deploy
When deploying from a Github commit, can you make the Realm files only update what is being committed? It seems like Realm is updating all files, which is taking forever when you have a bunch of functions, along with Hosting files, which in my case is a good bit.
If I go directly into the UI and update a function from there, the Deploy happens fairly quick. But, as soon as I commit from Github, that function gets updated by what is in my Github Repo, which in this case, would overwrire what I just did in the UI.
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 -
Support for Twitter Authentication
Currently, you only support Google and Facebook for social logins. Can Twitter also be added?
3 votes -
Global Variables for Functions
Add global variables to Functions (so I don't have to pass around supposedly global variables to every function call).
Add support for typescript :)))
3 votes -
Built the new Stitich like Strapi
Advanced Nodejs/React/Vue/Angular Developers have tried Strapi for sure once or at least heard of it. It is a headless-cms/graphical UI for building APIs, The first thing that came into my mind when I tried Stitch + the new GraphQL feature was, Nice product but the UI Strapi gives you for creating Schemas/Data is something MongoDB needs in thair Stitch App to take off since nobody does this currently.
So my suggestion for Stitch is to have a Strapi like UI so we don't need to write Schemas manually, I'm sure this product will take off since everyone I talked to…
3 votes -
Send tags to Datadog Integration
We currently use Datadog for our monitoring and alerting. Previously we were using the labels functionality to add information to our clusters in Datadog. With the recent deprecation of labels, we're looking for this same functionality with tags
2 votes -
Support Multiple CRON Schedules Per Trigger
It's not uncommon to want different trigger schedules to run on different days of the week, notably weekdays and weekends. The current solution is to create separate triggers that call the same function, but ideally, a single trigger could support multiple CRON schedules.
2 votes -
Triggers on DB level rather than single collections only
Change streams support events on DB level or single collections, but triggers are limited to single collections. Which means that if we wanted to listen on changes in a generic way, we would have to setup a trigger for each collection and set them up with AWS EventBridge (and think about new triggers when new collections are generated).
Given that the underlying tech (change streams) supports DB-level subscriptions, we would really like to see that on the UI, too.
2 votes -
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…
2 votes -
One-way comparison of secret values
Can we have a method that compares a value in a function against a stored secret value. The method should just return true or false to indicate whether the values matched.
If we had this there would be no need to expose a secret through a value.
2 votes -
Allow setting up private connection between Atlas App Services and AWS Elastic Beanstalk
I would like to set up a private connection between my Atlas App Services app and my AWS Elastic Beanstalk instance. Basically I want my Elastic Beanstalk instance to only accept requests that are coming from one of my App Services functions. I don't want it to accept requests from anywhere else on the internet.
I know there is a way to set up private peering between an Atlas Cluster's VPC and an AWS VPC (which I could put my Elastic Beanstalk instance inside of), but there is not currently any peering functionality for Atlas App Services.
2 votes -
genuine environments separation
There should be a way to truly enable running an app in development mode while still running the production mode.
Currently Atlas App Services only enables a single state of the app
("no environment" / "testing" / "development" / "QA" / "production").
If an app is currently running in production and there is a need to test new changes on the web, i.e. API requests, the app needs to return to "development" state.
But what if the production state cannot be changed since the app serves using clients?!?!
There is no why to bypass this except for duplicating the entire…2 votes
- Don't see your idea?