SBOM via packit v2 #296
SBOM via packit v2 #296
Conversation
| @@ -32,13 +41,31 @@ func Build(buildProcess BuildProcess, logs scribe.Emitter) packit.BuildFunc { | |||
| return packit.BuildResult{}, err | |||
| } | |||
|
|
|||
| modCacheLayer.Launch = true | |||
There was a problem hiding this comment.
@TisVictress What was the motivation behind making the modules cache layer available at launch time?
There was a problem hiding this comment.
I did some more investigating and realized that it's currently not possible to access the SBOMs for layers that aren't marked for launch. See this conversation on a lifecycle issue implementing SBOM support. That means that currently, there's no way for an end user to access the SBOM generated by this buildpack unless the layer is marked for launch. (I'm guessing you already know this and it's why you marked the layer for launch?)
I don't think we should change this buildpack to mark the modules layer for launch – for security/hardening and optimization reasons we don't want the modules layer present in the app image. But unfortunately I think that means there's no way to test or use this feature until the lifecycle and/or pack makes the build SBOM available 😞 .
There was a problem hiding this comment.
@fg-j I needed to be able to test that the BOM files exist in the integration test.
There was a problem hiding this comment.
So, I pinged CNB folks about this, and it looks like there's now an PR to enable grabbing build-time BOMs: buildpacks/pack#1359
Since this work is blocked anyway, let's wait to see if the build-BOM feature lands soon. That way we can integration test without changing the API of the buildpack.
|
Closing in favor of #311 |
SBOM implementation for
mod vendorResolves #13