DefaultBuildpacks: use v3 API #1323
Merged
Conversation
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
…udfoundryClient> Signed-off-by: Daniel Garnier-Moiroux <daniel.garnier-moiroux@broadcom.com>
Signed-off-by: Daniel Garnier-Moiroux <daniel.garnier-moiroux@broadcom.com>
13 tasks
pivotal-david-osullivan
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is part of porting
operationsto use the V3 API (#1325)Two commits:
DefaultBuildpacksconstructor to use a cloudFoundryClient instead of aMono, which drastically simplifies the code. It was already passed in as a value wrapped inMono.just.DefaultBuildpacksto use the v3 API instead of v2. It requires adding some waiting logic increateandupdate, because the "upload" operation is not synchronous.