Sambhav Kothari

If you are okay with using just the kpack build resource (instead of the image resource) , you should be able to use gcp buildpacks by directly specifying the builder...

@spew Thanks! We have also been updating https://github.com/buildpacks/libcnb to support these new SBOM apis. We also have a buildpack author's tooling team on the Buildpacks project now and would love...

Amazing! You should be able to find the details at https://github.com/buildpacks/community#details-5

+1 I am currently exploring the possible of using container-structure-test as a declarative testing utility for https://buildpacks.io (See https://github.com/buildpacks/rfcs/pull/205 and https://github.com/samj1912/buildpacks-venom-executor/blob/3360e7afbc518dac953a2f74daebb299a03f8a6e/examples/paketo-go/test.yaml#L18 for a POC). Would be happy to help out...

This is unlikely to be a trivial project. So far the jmespath functions we have created are simple extensions. The proposed filter (`let`) however is a change in the syntax...

Created a draft PR at https://github.com/pivotal/kpack/pull/686 to discuss what needs to be parametrized and how to add it to the release process.

Only if the total object size is larger than 1mb

If the image tagging strategy was previously None and then changed to BuildNumber, it will still override the provided tag, but the previous image will be left untagged and garbage...

That leads to a slightly non user friendly experience as they have to resolve the revision to a SHA. It could also helo with the trigger workflow I described above...

@tomkennedy513 / @matthewmcnew this will have quite a bit of an adverse effect on the resource utilization of the final build pod. Currently the resource utilization is calculated by max(max(init...