Open samdoeswork opened 11 months ago
@samdoeswork Thanks for opening an issue.
You should create a deployment every time you want to modify code or configuration. Deployments are immutable snapshots of your code, dependencies, and configuration.
The ability to make deployments unroutable (delete) is on the roadmap.
Thanks for the quick response
Hello @lucacasonato are there any updates on this? I noticed the new CLI allows for the deletion, but don't see anything in the UI yet.
What problem are you trying to solve?
Hi, when looking at the API documentation (and indeed the dashboard) it appears that we can only create new deployments.
There is no documented way to delete or update the old deployment.
This strikes me as risky - if there's a bad build, leaked secret, etc. it just persists?
Describe the solution you'd like
Ability to explicitly delete deployments.
Do you also have any recommendations for users iterating on code (e.g. run it with eval?) - it seems unlikely that every time the user saves code the correct thing is to create a deployment.
Describe alternatives you've considered
NA
Documentation, Adoption, Migration Strategy
The /delete equivalent to the get deployment details endpoint