spinframework / spinframework/spin-operator
Consider moving CRDs to separate Go module
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
If in a separate go module, other projects, such as the spin-kube plugin could reference it.
Context: https://github.com/spinkube/spin-plugin-kube/issues/88
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 CRD definitions and the current Go module boundary, then review the spin-kube plugin issue linked in the context. Determine how the CRDs can be consumed as a separate module; done means another project such as spin-kube can reference that module cleanly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100