We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the solution you'd like:
Currently witness policies support embedding base64 encoded rego packages to evaluate predicates found in a witness collection for a particular step:
{ "type": "https://witness.dev/attestations/command-run/v0.1", "regopolicies": [ { "name": "expected command", "module": "cGFja2FnZSBjb21tY..." } ] },
What currently isn't possible though, is to provide extra inputs to configure parts of the rego policy to evaluate (or not):
{ "type": "https://witness.dev/attestations/command-run/v0.1", "regopolicies": [ { "name": "expected command", "inputs": { "expect_sarif": true, "deny_no_fail": true }, "module": "cGFja2FnZSBjb21tY..." } ] },
Also, rego bundles could be a way of supporting common logic to be written that can be shared across multiple rego packages.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the solution you'd like:
Currently witness policies support embedding base64 encoded rego packages to evaluate predicates found in a witness collection for a particular step:
What currently isn't possible though, is to provide extra inputs to configure parts of the rego policy to evaluate (or not):
Also, rego bundles could be a way of supporting common logic to be written that can be shared across multiple rego packages.
The text was updated successfully, but these errors were encountered: