stackabletech / stackabletech/operator-rs
Improve label mechanisms
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 167
- Forks
- 19
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
- Objects which needs labels should be able to be created (via a builder) without setting those labels.
- Producing and consuming labels (and annotations) between different APIs must be simpler. Promote using strict types over plain strings.
- ...
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
No files, tests, or entry points are named. Start by locating the APIs for labels and annotations, then clarify how builders may omit labels and how labels should be exchanged between APIs. Done means the proposed label and annotation handling is simpler and uses strict types rather than plain strings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100