stackabletech / stackabletech/operator-templating
chore: Only put common stuff in the templated `default.nix`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 10
Description
note(non-blocking): We should only put common stuff in the templated
default.nix. All other operator-specific stuff should not be templated and should live in the operator repositories. @NickLarsenNZ will look into that.
Originally posted by @Techassi in https://github.com/stackabletech/operator-templating/pull/455#discussion_r1820837906
Contributor guide
No contributing guide indexed for this repository
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 with the templated default.nix and the discussion in pull request 455, especially the referenced comment. Determine which content is common across operators and which is operator-specific; this is done when only common content remains in the template and the other configuration lives in operator repositories.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100