spcl / spcl/serverless-benchmarks
Cleaning up inactive resources
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 199
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
SeBS keeps a list of cached cloud resources. However, the cache entries can become stale and invalid - this primarily applies to local deployment, where containers will be easily removed. Right now, a cached but removed container will throw an exception and force users to manually fix cache entries. We should be able to do it automatically.
- Detect old containers and reject them, issuing a warning.
- Add option to
sebs resourcesto clean up local containers. - Add option to
sebs resourcesto look for and stop remove orphaned containers, e.g., Azure CLI after crash; a complete killswitch.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the sebs resources command and trace how cached cloud resources and local containers are discovered and validated. Check how Azure CLI resources are handled after a crash. Done means stale containers are rejected with a warning and the command can clean up local and orphaned resources as described in the checklist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cli, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100