bottlerocket-os / bottlerocket-os/twoliter
make Infra.toml path configurable for twoliter commands that use it
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 34
- Forks
- 45
- Avg merge
- 11h 13m
- Merged PRs (30d)
- 16
Description
Bottlerocket has been fine because it is using `twoliter make` and can change the Infra.toml path via the env var in the twoliter's Makefile.toml.
However for OOTB builds using the proper Twoliter interface, users will need to be able to specify the location of Infra.toml. Affected commands
- `twoliter build variant`
- `twoliter build kit`
- `twoliter publish kit`
Are `twoliter fetch` and `twoliter update` affected? (I don't think so.)
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 at the command entry points for `twoliter build variant`, `twoliter build kit`, and `twoliter publish kit`, then trace how each locates Infra.toml. Define completion by allowing the Infra.toml location to be specified for those commands and confirming whether `twoliter fetch` and `twoliter update` are unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100