inspector: support flattened buildpacks #270
Merged
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.
With platforms introducing the ability to create flattened buildpackages,
the idea of 1 layer = 1 buildpack is not always true anymore - a single layer can contain multiple buildpacks.
This change adds to the inspector the ability to read buildpack metadata off flattened buildpacks.
This fixes
jam summarize
when creating summary/release notes for flattened buildpacks.Previously it picked up the first
buildpack.toml
it could find in the layer, and assumed it to represent the buildpackage.Checklist