Render should automatically spin up a full service group (APIs, web frontends, Redis, databases) when a PR is created so it can be tested in isolation. When the PR is merged or closed, the environment should be deleted automatically.
Note: this is currently supported by render.yaml. Please send us a message in render.com/chat if you'd like access to the feature.
Currently in early access.
We've been testing a feature that lets you create a group of services for a given pull request; including databases and support for running migrations at the start. Please get in touch in chat at render.com/chat if you'd like access.
@Anurag Goel: Will the PR services be able to access the main services?
I can see how you might want it both ways:
NO: security to prevent PR services doing damage to production infrastructure.
YES: You might have a dependency on something that is not in the group (is that possible) and then you still want PR services to be able to access that.
@Steven Borrie you can create Preview Services in a different team (say Development vs Production); teams do not share networks so your production services won't be affected accidentally.