Postgres 12 was released in 10/2019 and offers many new and important features we already use across all our apps. Please make Version 12 available so we can migrate our databases to render.com
I'd like to see database memory (done), CPU (done), active connections and logs. Bonus: slow query list.
Basic HTTP Metrics
For HTTP services, it would be great to see some basic stats like # of requests by status code, etc. in the "Metrics" tab of the application
This would be useful for * Running one-off commands on services (e.g. migrations) * Tailing service logs
Create a terraform provider for Render's IaC
This would allow users to manage infrastructure across different services using a single tool.
I want Redis to be supported like Postgres. I don't want to think about restarts, health checks, or ensuring the service is running. I don't want to mess with the config to make it fast.
2FA enforcement for teams
Achieve higher security overall by enforcing all members of my team to first enable 2FA before they can do _anything else_.
Enable Native Static Outbound IPs
Some applications use third party hosted databases like MongoDB Atlas or Google Spanner, which can be secured with an allowed IP list. Render users can now use https://www.quotaguard.com as an addon to get a static outbound IP for all their services. This feature requires setting up QuotaGuard through the Addons screen in the Render dashboard. Allow users to request and enable static outbound IPs for some or all of their services natively without QuotaGuard.
Skip deploy based on commit message
With most CI systems, if I put [ci skip] or something into the git commit message, then we can skip a CI flow for that commit. This is useful for stuff like typo fixes to READMEs, etc. I would like to be able to put [render skip] into the git commit message to skip the Render deploy. Ideally either of these would behave identically: [render skip] , [deploy skip]
Multiple environments in a single render.yaml file
It would be super useful to be able to do something like this in the render.yaml file: environments: - name: my-project-prod previewsEnabled: false services: # ... envVarGroups: # ... databases: # ... - name: my-project-staging previewsEnabled: true services: # ... envVarGroups: # ... databases: # ... It's basically "just" nesting the current content of the render.yaml file into the environments array. This would enable workflow such as having prod without preview environments and then having staging with preview environments. Workflow like that is currently impossible to achieve when I want to use infrastructure as a code.