-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request: The lifetime of deployments is not clear to me #18
Comments
All deployments exist forever. Each deployment has its own uniquely generated URL, which you could use to test against for example or verify changes are working before pushing to production. Deployments marked as production still have a unique URL, but also get assigned the project domain(s) when successfully deployed. Its possible for us to prevent deployments from being accessible after a certain time frame, but this isn't implemented. |
I believe that from a DevOps and security perspective, it would make sense that a developer can turn off access to and completely delete previous deployments. What happens if I have a vulnerability for example that was previously deployed that I want to delete? Would you also charging in the future for these environments existing (Especially if I have data or other things as part of my deployment)? |
Makes sense, we can quite easily delete those deployments - just not possible at the moment (will make a feature request). Could you clarify on what you mean by "data" in the deployment here:
There will be no change keeping old deployments around on our side, it's part of the architecture decision we made and built. |
I am interested in the "easily delete those deployments" feature as well. Is there an option to delete a project entirely (not just a deployment)? What about deleting an account? |
Thanks for the feedback, once we complete the road map it'll give more insight into what we're working on. Yeah project and account will be implemented - deleting a project is partly done but needs more tests on our side. |
Is there an existing feature request for this?
Description
As a developer, when I deploy a version of my backend it is not clear to me what the lifetime of that deployment is, and whether I can delete the old deployments from having to show up in my console.
Reasoning
I think it would make sense to have only a handful of environments that are active at any point in time. And I cannot see a way to understand (from the console or from docs) on what the lifetime of my deployments are. Will the links created by Globe continue to be alive at all times?
Additional context and comments
No response
The text was updated successfully, but these errors were encountered: