Add support for building composite buildpacks #63
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.
Summary
This PR resolves #48. It adds the ability for
libpak-tools package bundle
to build composite buildpacks. It does nothing fancy and is just a wrapper around the similar pack command, but it does help to enforce some default settings so it should be as easy aslibpak-tools package bundle --buildpack-id paketo-buildpacks/java
to build the composite.You can then manually adjust
package.toml
and point to local images, rebuild and get a composite image with custom buildpack changes.In addition, it fixes a bug where a missing
BP_ROOT
was ignored, which was confusing. It also does a little refactoring renaming some variables to better indicate intent.Use Cases
Build composite buildpacks.