osbuild / osbuild/image-builder
Determine which modules should be enabled with user-provided kickstart blobs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 77
- Forks
- 103
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 53
Description
https://github.com/osbuild/images/pull/631#issuecomment-2113140898
- We don't want to parse user blobs.
- We want users to be able to do things like add users, which requires a module that we generally enable conditionally.
- Do we also want users to be able to make an unattended/automatic ISO without needing to specify everything? That would require module control.
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 with the discussion linked from pull request 631 and review the existing decisions around user-provided kickstart blobs. Clarify whether users should be able to add users and create unattended ISOs without specifying every module. Done means the module-enabling policy and required control behavior are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100