towardsthecloud / towardsthecloud/cloudburn
Schedule Idle Resources scans
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
Let customers schedule recurring Idle Resources scans for each connected AWS account in their preferred timezone.
Why
Automatic scans keep cost cleanup continuous without requiring someone to remember and start every review manually.
Scope
- Offer daily, weekly, monthly, custom, and manual-only schedules
- Preview the next run in the selected timezone
- Pause, resume, or remove a schedule per account
- Explain skipped or failed scheduled scans without creating duplicates
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
The issue does not name files, tests, or entry points. First trace how Idle Resources scans are started for connected AWS accounts and where account settings are stored; then map scheduling, timezone, lifecycle, and duplicate-prevention behavior. Done means all listed schedule modes and controls work per account, with next-run previews and clear skipped or failed scan explanations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100