chore(oscap): re-pin CA bundle hash and fixture base-image digests - #136
Closed
octo-sts[bot] wants to merge 2 commits into
Closed
Conversation
Atomically updates the CA bundle SHA in the OSCAP datastream, the digest-pinned FROM lines in tests/e2e/fixtures/*/Dockerfile, and the pinned wolfi-base digest in the offline harness test (TestParseWolfiBaseRef) so the three values can never drift out of sync (which would flake the CertificateAudit E2E assertions or break the offline unit tests). Image: cgr.dev/chainguard/wolfi-base:latest Digest: sha256:003627df3c1e1bba0c4116afcddb314aca9594ee2328c7e876a8081a6c988b2e CA SHA: 61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9 Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…d15ac7f33c4ece861aaef8c7d7a519cd1d9
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
CA Certificate + Fixture Base-Image Update
Atomically re-pins three values that must stay in lockstep:
<ind:hash>underoval:org.CABundleHash:ste:1in the OSCAPdatastream (
gpos/xml/scap/ssg/content/ssg-chainguard-gpos-ds.xml).FROM cgr.dev/chainguard/wolfi-base:latest@sha256:...line inevery
tests/e2e/fixtures/*/Dockerfile.pinnedwolfi-base digest constant asserted byTestParseWolfiBaseRefintests/oscap-offline/internal/scan/fixtures_test.go.If these drift (e.g. Dependabot bumps the fixture digest before this
workflow refreshes the datastream hash, or vice versa), the
baseline-clean/cabundle-tamperedE2E CertificateAudit checkfails because the fixture's CA bundle no longer matches the hash the
datastream asserts, and the offline harness unit tests break against
the stale test pin. This workflow is the authoritative update point
for all three values together;
TestParseWolfiBaseRefwas runagainst the updated tree before this PR was opened.
cgr.dev/chainguard/wolfi-base:latestsha256:003627df3c1e1bba0c4116afcddb314aca9594ee2328c7e876a8081a6c988b2e61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9falsetruetrue