+1 to the request to restrict access to deploy previews from the public Internet
Another idea might involve letting devs hide/unhide deploy previews automatically based on their site’s config. It’d be nice to have a preview hide after its PR merges, but then still have the option to unhide it selectively if needed (i.e. to share with a customer, etc.).
That might help uphold part of the reusable permalink philosophy that @jen and @fool mentioned last year.
And yet another +1. Once the PR gets merged and the branch deleted, I would expect the preview to be deleted too, or at least have the option to do this manually. I’ve shared preview urls to clients to check out beta versions, and once the feature is merged, I want to make sure the clients stop using the deploy preview URL.
It would be ideal to be able to disable those URLs.
Edit: it seems like it might be happening a few seconds after each deploy. Is it a Netlify bot?
Please consider the urgency of this. Looking at other responses in this issue and my own concerns with this missing functionality is tipping towards desperately finding another service provider!
Don’t get me wrong, I absolutely LOVE Netlify and currently recommend it to everyone I come across that haven’t already heard of it (for example the 90 people I talked to in a fullstack developer class)… but not having control over deploys (especially PR deploys) lifecycle is a dealbreaker (in the long run).
Again, I really want to be able to stick with Netlify and move all my old and future clients there. But I can’t do that in good conscience if there might be uncontrollable versions of the site floating around.
Thanks again for one of the best online products in years!
No changes over the behaviour of PRs any time soon, I’m afraid.
It’s always an option to set up two sites, one as a staging environment and one as production where only changes which are merged to the production branch get pushed to the production site. Then, you could run a cleanup on the staging env site ad-hoc, or periodically.
One concern is, are all PRs only reachable with the permalink (i.e. is there a robots.txt)? Wouldn’t want a PR deploy showing up in a search result for whatever reason down the road
Consider features like this! Very easy to avoid duping data with canonical headers.
Just want to chime in here to add my +1 on the importance of being able to delete deploy previews. I was shocked when I merged a branch and the deploy preview didn’t disappear, and then I was unable to find any way to delete it! It at a minimum should be very clear up front when a user turns on this feature that these things live forever.
+1 to deleting deploy previews when the branch is deleted. I’d like to also request that the URL is not trivially guessable (or, far better, add an option to restrict the previews with password protection). Have to disable this really great feature in the meantime :-/. Thank you.
Creating an alternate test site where the entire thing is password protected could work. That would make it OK to have deploy previews with easily guessable URLs. And as previews accrue, it could be periodically deleted/rotated. Thank you for the suggestion.