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, legacy BOMs output by buildpacks (either because the buildpack api < 0.7 or for backwards compatibility with older platforms - see here) end up in the io.buildpacks.build.metadata label on the app image. This can cause very large labels which can take down k8s nodes.
The linked PR would remove legacy BOMs from the io.buildpacks.build.metadata label. It would also remove the [bom] table from layers/config/metadata.toml (for launch boms) and report.toml (for build boms).
To allow newer platforms to maintain compatibility with older buildpacks, it has been suggested to copy legacy BOMs to /sbom/launch/legacy.sbom.json and /sbom/build/legacy.sbom.json.
The text was updated successfully, but these errors were encountered:
See related spec PR: buildpacks/spec#288
Description
Currently, legacy BOMs output by buildpacks (either because the buildpack api < 0.7 or for backwards compatibility with older platforms - see here) end up in the
io.buildpacks.build.metadata
label on the app image. This can cause very large labels which can take down k8s nodes.The linked PR would remove legacy BOMs from the
io.buildpacks.build.metadata
label. It would also remove the[bom]
table from layers/config/metadata.toml (for launch boms) and report.toml (for build boms).To allow newer platforms to maintain compatibility with older buildpacks, it has been suggested to copy legacy BOMs to /sbom/launch/legacy.sbom.json and /sbom/build/legacy.sbom.json.
The text was updated successfully, but these errors were encountered: