denoland / denoland/deploy_feedback
Option to stop old instances or prevent preview Deployments
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
I was playing around with Deno Deploy and Discord bots and noticed that I start getting old code behavior and realized that there were multiple instances running and no option or way to prevent old instances of code to run in the Deno Deploy hosting environment.
A way to kill off preview deployment instances or even better an option to prevent them from being created in the first place would be great option.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue mentions Deno Deploy hosting and preview Deployment instances but names no files, tests, or entry points. Start by locating the preview Deployment lifecycle and its instance-management settings; clarify whether stopping existing instances, preventing preview creation, or both is required, then define tests for the selected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100