Allow 'oem' scheme for source url
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Created originally in Butane by @mpu-ssg: https://github.com/coreos/butane/issues/634
Currently experimenting with Flatcar, I'm using butane to generate my ignition file.
Documentation suggests the use of oem:/// to retrieve files from /oem partition during ignition phase.
With the special oem:/// file URL the config can copy files from the OEM Partition to the root filesystem
I haven't found any issue about this topic. Also it appears Ignition specification does not mention this, even the Flatcar one (https://www.flatcar.org/docs/latest/provisioning/ignition/specification/).
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 repository files, tests, or entry points are named. Start by reading the referenced Flatcar OEM-partition documentation and Ignition specification, then trace source URL scheme handling in the repository. Done means the oem scheme is accepted consistently with the documented behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100