Atlas App Services
43 results found
-
Add Null Type Schema Validation to realm-cli
The realm-cli is already quite powerful in managing the Atlas Apps, but we are missing the setting 'Null Type Schema Validation'.
In a multi-stage environment, this lead to some environments failing validation while others did not fail.
The settings should also be included in the realm-cli pull, push and diff command
1 vote -
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 -
Enlarge the coding window by uplining the "Add Dependency" button
It seems like the single and not frequently used button of "Add Dependency" could very well fit in line with the "Function Editor" and "Settings" buttons, and all the space allocated for it could make more room for the main focus wich is the coding window.
3 votes -
Environement values storing JSON Object
The ability to set an environement value as a JSON Object.
It is currently possible but working locally with realm-cli and pulling changes the JSON Object environment values are converted to arrays.1 vote -
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 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 -
Support device notification
OS notification API via a mongo collection to improve developer UX and make mongodb the best way to pull off this difficult mission.
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 two factor authentication
It would be great to have an option for two factor authentication to increase security. Ideally this would be via authentication apps such as Microsoft Authenticator, email or SMS authentication would be viable too.
17 votes -
Add support for GitLab
As an alternative to using GitHub
5 votes -
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 -
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 -
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 -
More flexible Custom User Data / User Linking
On Stitch, you can have multiple providers for identity, but then it creates multiple users even with the same email address if you have someone from say Google or then someone who authenticated via email. There is a way to merge two accounts, but it requires the user to authenticate twice and that's not an ideal user experience. One solve is to treat them as one user. The other solve is to create a user metadata collection which both identities can reference, but if you're trying to add rules and permissions you can't put an array of options in the…
38 votes -
Automatically Refresh Auth Tokens on User's Custom Data Change
Currently, getting updates to custom user data on the frontend requires periodically refreshing the token. A potential improvement would be for MongoDB Realm/SDKs to detect these changes automatically and streamline the token refresh so application code wasn't required to handle this case.
35 votes -
Programmatic Support for Uploading Dependencies
Right now the Realm Administration APIs [1] only let's users list dependencies. It would be helpful to have an endpoint to upload dependencies as we have 8 env and uploading manually to all envs is painful.
[1] https://docs.mongodb.com/realm/admin/api/v3/#dependency-apis
2 votes -
8 votes
-
Schema for Realm's JSON Files to Enable Auto-Completion
This is a minor suggestion but it will be great if intellisense works for Realm-specific json files (i.e. "auth_providers/api-key.json", "services/mongodb-atlas/rules/db.collection.json", etc).
It will be helpful for developers using the Ream's "Deploy with CLI/GitHub" feature (which is great). I guess it may help reduce confusions; for example ObjectId/ObjectID/objectId.
VSCode has built-in support for JSON schema, and it seems additional schemas can be specified via three options: $schema in the file, VSCode settings or an extension.
https://code.visualstudio.com/Docs/languages/json#_json-schemas-and-settings5 votes -
Migrate Firebase Cloud Message from legacy HTTP to HTTP v1
I am very happy with Push Notifications using FCM but currently, FCM has been update to HTTP v1 and I saw that MongoDB Push Notification still using the HTTP. With HTTP, I can't send an image in the notification payload (https://firebase.google.com/docs/cloud-messaging/android/send-image), also the data payload is different when I send message directly from FCM.
I hope that MongoDB have plan to migrate Firebase Cloud Message from legacy HTTP to HTTP v1 (https://firebase.google.com/docs/cloud-messaging/migrate-v1)
1 vote -
Local development tooling
Similar to AWS SAM (https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-invoke.html) or Google Cloud Functions Framework (https://cloud.google.com/functions/docs/functions-framework).
I.e. the ability to run functions locally. It's expensive and slow to have to run and test code in a project remotely all the time even for small changes.
156 votes
- Don't see your idea?