oxidecomputer / oxidecomputer/vw
Add time-to-live (TTL) option for cloud environments
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 1
- Avg merge
- 32m
- Merged PRs (30d)
- 5
Description
For environments created by automation, particularly CI automation. It would be good to have TTLs on such environments so if something goes sideways with the automation in a way that leaves the environment dangling, there is a vw-svc mechanism to clean it up.
Contributor guide
No contributing guide indexed for this repository
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 by reading the vw-svc environment lifecycle and the automation or CI paths responsible for creating environments. Determine where a TTL could be configured and enforced, and define done as ensuring abandoned automated environments are cleaned up after their TTL expires.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100