towardsthecloud / towardsthecloud/cloudburn
Organize cost findings into focused profiles
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
Organize CloudBurn Platform cost findings into four stable profiles: Unused Resources, Resource Efficiency, Commitment Savings, and Cost Governance.
Each supported check will appear in one clear customer-facing category, with intentional exclusions explained.
Why
Consistent categories help customers understand what action to take and make scan results easier to navigate over time.
Scope
- Define stable names and descriptions for the four optimization profiles
- Assign each supported check to one profile without duplication
- Version profile membership so saved scan results remain understandable
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 by locating the cost findings and supported checks in the CloudBurn Platform codebase. Define the four profile names and descriptions, assign each supported check exactly once, document intentional exclusions, and version membership so saved scan results remain understandable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100