Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add conflict to cosign_sign #92

Merged
merged 1 commit into from
Oct 31, 2023

Conversation

jonjohnsonjr
Copy link
Collaborator

The default is APPEND, which matches the current behavior today. This adds both REPLACE and SKIPSAME to match what cosign_attest does. Instead of using predicateType as the replacement criteria, this uses the signature layer's digest.

It should be safe to bump this before we bump terraform-publisher-apko because the default matches the current behavior.

@jonjohnsonjr jonjohnsonjr force-pushed the sign-conflict branch 3 times, most recently from baad44d to 8e32644 Compare October 21, 2023 00:08
@jonjohnsonjr jonjohnsonjr force-pushed the sign-conflict branch 3 times, most recently from d0e1a77 to 3a97b59 Compare October 31, 2023 02:36
The default is APPEND, which matches the current behavior today. This
adds both REPLACE and SKIPSAME to match what cosign_attest does. Instead
of using predicateType as the replacement criteria, this uses the
signature layer's digest.

It should be safe to bump this before we bump terraform-publisher-apko
because the default matches the current behavior.

Signed-off-by: Jon Johnson <[email protected]>
@jonjohnsonjr jonjohnsonjr marked this pull request as ready for review October 31, 2023 03:20
@jonjohnsonjr jonjohnsonjr merged commit 50e1f6a into chainguard-dev:main Oct 31, 2023
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants