-
Notifications
You must be signed in to change notification settings - Fork 62
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
chain bench config file and output assertion rules #57
Comments
Something like so {
"quiet":true, // Other configurations here
"rules": {
"https://github.com/aquasecurity/*": { // Supporting wildcards
"fail":{
"1.1.3": {
"result":"Failed"
},
"1.1.14": ["Failed","Unknown"] // Alternatively supporting couple of results
}
}
}
} So everytime you run chain-bench against any repository in aquasecurity the following rules will be applied |
Like that! will be great feature, we'll take it 🙏🏽 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My idea here is creating a
.chain-benchrc | chain-bench.config.json
file that the repository will holdAnd upon running the cli in the context of that repository it will read that config file for any configuration for chain-bench
Leveraging that config file, add
rules
key into the json with sub keyspass
andfail
those will hold assertions over the json output of chain-bench that will decide what will be the exit code.For now when I want to assert over the chain bench output (JSON format), I am doing it with
jq
orrego
.The text was updated successfully, but these errors were encountered: