Feature Requests

We have an app that is deployed via Docker image through a Deploy Hook call from Github Actions. It would be great being able to pass a description to the Deploy Hook URL so we can have a custom deploy description in the deploy timeline events, such as the commit message of the commit related to the deploy.

I would like to be able to use any monitory service I want for my managed services like postgres. This usually requires allowing this third-party to scrape opentelemetry metrics from your services. Easily doable when you control the runtime, but not so much when it is a managed service like Postgres or a load balancer. Example of very important metrics: Rate of status code (especially 5xx and 4xx) RAM/CPU usage in the database

This would be useful for putting staging/development environments behind a company VPN to prevent unauthorized access.

Deno ( https://deno.com/runtime ) is a modern, fast JavaScript runtime (from the originators of Node.js). I'd love to use Render for Deno-based web services instead of Node.js-based web services. It should be very simple to adapt what you have for Node.js web services and tool it for Deno instead. (Deno is actually simpler than Node.js + npm, a single all-in-one executable that is both the runtime and the package manager, etc.)

Many people use the same Git repo/build process for multiple instances (Web service, private service, cron job etc.). This cases the same build happens multiple times in parallel, wasting resources. It would be great if builds could be shared among services, seeing as builds are already saved (i.e. for rollbacks).

Add Sao Paulo region

show some love for the south americans :D

It would be great to be able to configure paths for blueprints when connecting them. There are some use cases which would be trivially covered by that: - mono repos - multiple environments * dev, staging, production * demo * maybe even multitenancy (for few tenants)

We build our Blueprint yaml from a template and want to sync changes to the blueprint only after some checks were done or depending on the branch/tag/... Therefor it would be preferable if we could "manually" trigger the blueprint sync in the CI/CD pipeline. Through a hook/API call/.... The only current solution would be to call the API/get the blueprint/update the blueprint for autosync/ wait for the sync to happen/update the blueprint to disable autosync. It's doable but tedious

Sometimes, a service is dependent on another service, like when a background worker is dependent on the main service getting updated and running migrations. It would be nice to be able to define this relationship in Render, so things like deploys can run sequentially.