Serverless Functions

I would like to allow my function to talk to a database secured behind a VPC, but for whatever reason VPC does not seem to allow Function assignment to the network. Exposing my database to a public IP does not seem like a good option here.

Currently there is no way to provision the FaaS offering from DigitalOcean with Terraform. Please add a way to define functions, routes, entry points, environment types, etc.... I see that you can define serverless functions deployed through the app platform, but the definition is highly limited, and requires the project.yml file to be used as well. We should be able to define and deploy serverless functions, through the app platform and standalone namespaces, through terraform alone.

Currently Cron triggers don't account for Daylight Savings time, this is a problem because triggers will start to go off at the wrong time without the user even realizing it unless they manually change the time every single year. Please account for DST! Thank you :)

to trigger file processing upon completion of an upload. AWS supports this with S3 events and SNS/lambda, and GCP has this with a Cloud Storage trigger to Cloud functions. as also requested here: https://www.digitalocean.com/community/questions/will-spaces-have-file-events-that-can-trigger-functions

If a managed database has connections restricted to trusted sources, it is not possible to connect to it from serverless functions deployed to namespaces (outside the App Platform). Consider adding an ability to specify a function, package, or namespace in the list of trusted sources of a database.

I've been an early-adopter for a while of your services; Rust isn't new, and is EXTREMELY fast in a serverless environment, less prone to pauses / hangs than Go, and has a similar footprint in size when compiled. Not to mention it's safer than any other language you support.

If you want to deploy your serverless functions to the App Platform, you need to use remote build. But it can only access lib and packages folders. This doesn't work well in monorepos where you want to share some code with your apps. In fact, functions in such monorepos cannot even be built since they rely on the root package.json and node_modules which are not available in remote build. Remote build should either be able to access any file in a given repository or it should be possible to specify not only which runtime files are included in a function but also which build files are needed.

Now that DO supported OpenSearch for DB clusters & App Platform, it would be great to see this rolled out onto functions as well; as the logging is fairly limiting.

Like aws lambda it would be convenient if one can upload/access/modify multiple files through control panel.

Would badly like the equivalent of Azure Table storage on DigitalOcean: https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-overview "Azure Table storage is a service that stores non-relational structured data (also known as structured NoSQL data) in the cloud, providing a key/attribute store with a schemaless design. Because Table storage is schemaless, it's easy to adapt your data as the needs of your application evolve. Access to Table storage data is fast and cost-effective for many types of applications, and is typically lower in cost than traditional SQL for similar volumes of data. You can use Table storage to store flexible datasets like user data for web applications, address books, device information, or other types of metadata your service requires. You can store any number of entities in a table, and a storage account may contain any number of tables, up to the capacity limit of the storage account."