Gustav Westling

This bug (or lack of feature) caused an outage for me recently. A rolling restart of kube-router was performed to get a configuration change out. When the new pods started...

> Do you mean that closures are currently not supported? Yes, exactly. The compilation of the following program will fail: ```go package main import "external" func main() { foo :=...

I'd really like to implement closures one day, I've never implemented it in a language, so it should be a fun challenge! Inspiration to work on tre usually comes back...

@kmarteaux First, thanks for working on this! But yes, I don't know if this feature really fits in kube-score. We already have configurations etc, and this feels like it might...

Looks like the code doesn't compile anymore, I'm guessing that we need to make some alterations to our `sarif.go` to make it fit how the library is supposed to be...

Ah, ok, no worries! :-D

@s-m-sufyian Sure, do you have any ideas for how to solve this in a reasonable way?

Hey, you can utilise your shells filename expansion features and achieve this with `kube-score score build/*`. Generally I don't think that kube-score should incorporate features that other tools can do,...

> and (b) they do not show affected filenames They do! In the default output format kube-score doesn't display the file paths (the json and serif formats do), but the...

Hey, As I see it, this is by design, to avoid cascading failures, read [README_PROBES.md](https://github.com/zegl/kube-score/blob/master/README_PROBES.md) for more information about why this exists. If you don't agree with this, and have...