1
Limitation on returned stdout and stderr values from Cloud Functions
Source: appwrite/appwrite#3253 · opened by @arcanechimp
Is this env variable mentioned in PR still going to be added?
I would like to use the Cloud Functions as a way to access data from a seperate cache and database whilst using Appwrite's authentication, and being able to change the max value would be very helpful to achieving this.
If the reason for the limitation is imposed to fit within the MariaDB string field size constraints, could the value just be truncated for storage in the logs, and the limit be removed entirely for the actual execution object returned from the function?
I would like to use the Cloud Functions as a way to access data from a seperate cache and database whilst using Appwrite's authentication, and being able to change the max value would be very helpful to achieving this.
If the reason for the limitation is imposed to fit within the MariaDB string field size constraints, could the value just be truncated for storage in the logs, and the limit be removed entirely for the actual execution object returned from the function?
No pledges yet. Be the first to back this.
Comments
Similar requests
Using total VS sum for API responses when querying lists of data
4 votes · 0 comments
🚀 Feature: Cloud functions keep alive
1 vote · 0 comments
Visual node builder for functions
1 vote · 0 comments
🚀 Feature: Allow to pull settings from appwrite cloud functions
0 votes · 0 comments
Let's talk about Appwrite's permissions
7 votes · 0 comments
No comments yet.