stackabletech / stackabletech/operator-rs
Builders in a seperate crate?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 167
- Forks
- 19
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
I'd love to use the PodBuilder and other builders currently provided by this crate, but I feel that since this crate hasn't been published it doesn't seem like it's stable.
I'm hoping that your Builder API can stabilise and possibly be a seperate crate to be consumed as it is a great way to create the necessary Kubernetes objects (instead of the serve_json::json! mechanism).
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 reviewing the PodBuilder and other builder APIs mentioned in the issue, then compare them with the serve_json::json! mechanism and the repository's crate layout. Determine the intended public boundary and stabilization requirements for a separately consumable crate; done means the API and crate ownership are explicitly agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100