towardsthecloud / towardsthecloud/cloudburn

Compare Idle Resources scan history

Open
#155 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cloudburn-platform enhancement
Dominant language
TypeScript
Stars
1.8k
Forks
371
Avg merge
4h 32m
Merged PRs (30d)
63

Description

What

Let customers reopen earlier Idle Resources scans and compare two results for the same AWS account and region.

Why

History makes it easier to see whether cleanup work is reducing waste and which findings are new, resolved, or still present.

Scope

  • Search and filter scan history by account, status, trigger, and date
  • Reopen any retained scan result
  • Compare findings as new, resolved, or still present
  • Show trends in finding counts and potential savings

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the existing scan result and retention flows, then define how account, region, status, trigger, and date filters work. Done means retained scans can be reopened and two results clearly show new, resolved, and still-present findings with finding-count and potential-savings trends.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
analytics, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.