frontend: export frontend options / consts for external consumers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 48
Description
- relates to https://github.com/moby/buildkit/pull/3694
While looking at a ticket in moby/moby (https://github.com/moby/moby/issues/45665), I discovered more strings in there that have non-exported consts defined in BuildKit;
https://github.com/moby/moby/blob/8d67d0c1a8d28ad4014444edc6b9975f9877b1d6/builder/builder-next/builder.go#L299-L332
consts are in the dockerfile frontend;
https://github.com/moby/buildkit/blob/80b91c55a47feb52a66e143a3929e614dd5c7adc/frontend/dockerui/config.go#L26-L51
We should export those consts (and make them strong-typed) to help discovery and to allow Moby/Moby to consume them.
Originally posted by @thaJeztah in https://github.com/moby/buildkit/issues/3694#issuecomment-1571069116
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 in frontend/dockerui/config.go, where the Dockerfile frontend constants are defined, and compare them with the strings used in the linked Moby builder.go section. Export the relevant constants with strong types so external consumers such as Moby can use them directly; verify that the intended options and values remain discoverable and consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100