Create api interface to define build usage backend#49924
Merged
vvoland merged 1 commit intomoby:masterfrom May 13, 2025
Merged
Conversation
Avoid importing buildkit builder into api package when only a single backend function is needed. Signed-off-by: Derek McGowan <derek@mcg.dev>
17 tasks
Member
|
As a follow-up, we could consideradd this method (as a wrapper) to the backend/builder; moby/api/server/backend/build/backend.go Lines 32 to 38 in 453c165 Then we wouldn't have to pass two separate fields in builder options; Lines 434 to 449 in 453c165 Line 718 in 453c165 Line 730 in 453c165 |
vvoland
approved these changes
May 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Avoid importing buildkit builder into api package when only a single backend function is needed.
Related to #49873