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

Change the artifact_signature rule to use constraints evaluation, not deny-by-default #104

Merged
merged 1 commit into from
May 7, 2024

Conversation

jhrozek
Copy link
Contributor

@jhrozek jhrozek commented Apr 29, 2024

Because the artifact_signature rule uses the deny-by-default model all
we get from the evaluation in case it fails is denied. Especially for
artifacts this is not ideal as we can't tell the user what changed in
the artifact vs. the expected state unless they look at minder logs.

Fixes: #103

… deny-by-default

Because the artifact_signature rule uses the deny-by-default model all
we get from the evaluation in case it fails is denied. Especially for
artifacts this is not ideal as we can't tell the user what changed in
the artifact vs. the expected state unless they look at minder logs.

Fixes: mindersec#103
@JAORMX
Copy link
Contributor

JAORMX commented Apr 29, 2024

Let's brainstorm about this tomorrow.

Copy link
Contributor

@JAORMX JAORMX left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine given that we want to anyway refactor into smaller rule types in the future.

@jhrozek jhrozek merged commit 43ac564 into mindersec:main May 7, 2024
2 of 3 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.

The artifact signature rule doesn't expose any details about what failed
2 participants