You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when you package a buildpack offline with Jam, it will include all dependencies. With libpak you can use --dependency-filter multiple times to provide regular expressions that match dependencies to include.
Additionally you can use --strict-filters so that the regular expression needs to match the dependency ID as well as the Version. This allows users to provide a filter of (jre|^17.*) to only include that dependency for a specific version.
Possible Solution
The same functionality as libpak create-package. See above.
Motivation
Packaging offline buildpacks will often include many more dependencies than you know you will need and creates huge images that need to be pulled at build time.
The text was updated successfully, but these errors were encountered:
Describe the Enhancement
Currently when you package a buildpack offline with Jam, it will include all dependencies. With
libpak
you can use--dependency-filter
multiple times to provide regular expressions that match dependencies to include.Additionally you can use
--strict-filters
so that the regular expression needs to match the dependency ID as well as the Version. This allows users to provide a filter of(jre|^17.*)
to only include that dependency for a specific version.Possible Solution
The same functionality as libpak
create-package
. See above.Motivation
Packaging offline buildpacks will often include many more dependencies than you know you will need and creates huge images that need to be pulled at build time.
The text was updated successfully, but these errors were encountered: