You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this great project. ShiftLeft scan internally use this tool for scanning Kubernetes configuration files. Scan uses an open standard format called SARIF for reporting and can automatically convert a range of JSON files to this format.
Conversion of kube-score json (both v1 and v2) is a bit tricky but possible. The following mandatory attributes are however required, though.
File name (Name of the yaml file or stdin)
Line number
Severity (Text such as low, medium, high, critical)
Thanks for your help in advance.
The text was updated successfully, but these errors were encountered:
Hi @prabhu. It's cool to see that you've integrated kube-score into scan!
I agree with you that it would be great to have some traceability of where the configuration input was coming from and that this is something that kube-score currently is lacking.
Unfortunately it's not completely straight forward to add easily, so I'll add it to the backlog for now.
Contributions from you (and others) to contribute to this are welcome!
303: all: track file location in the parser and scorer r=zegl a=zegl
```
RELNOTE: Include file name and row of objects in the JSON output format (`--output-format json`).
```
This functionality is fairly basic, the filename and line points to the first line of the object in the input YAML.
This updates #256
Co-authored-by: Gustav Westling <gustav@westling.dev>
Thanks for this great project. ShiftLeft scan internally use this tool for scanning Kubernetes configuration files. Scan uses an open standard format called SARIF for reporting and can automatically convert a range of JSON files to this format.
Conversion of kube-score json (both v1 and v2) is a bit tricky but possible. The following mandatory attributes are however required, though.
Thanks for your help in advance.
The text was updated successfully, but these errors were encountered: