Anders Eknert

Given how most of the strict checks will be made default in OPA 1.0, I don't think there's any point in having them included in Regal at this point. The...

Reading [this blog](https://zenn-dev.translate.goog/erueru_tech/articles/6cfb886d92858a?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_hist=true) helped me understand that making compilation mandatory / opt-out would mean Regal would fail on many policies we're currently able to lint. > Finally, regarding the linter,...

First issue (`prefer-some-in-iteration`) fixed in #579. On to the next.

* We could also do simple unused checks on these, as we wouldn't need to scan more than the same AST. * We could perhaps forbid annotations on these as...

Another example would be "Weaveworks Policy Agent", which makes use of another CRD: https://github.com/weaveworks/policy-agent/blob/dev/policies/ControllerContainerAllowingPrivilegeEscalation.yaml Given that, perhaps it would make sense to allow configuring where to look for Rego inside...

That's an excellent point 👍 I'll take a look at how OPA does this, as ideally we'd provide the same JSON error output as OPA does for errors that originate...

Thanks @charlesdaniels! I'm not sure but we probably don't need rq integrated as a library in order to lint its files, we'll just need to be aware of that parsing...

This is mostly fixed with #96 , but we only do "top level" checks in rules with that, so I'm leaving this open hoping to come back to it later...

That's awesome @Parsifal-M 👍 Just create a new doc in the docs directory called `cicd.md` or something like that, and remember to add a link or two from the README...

While some enforcement of this rule could be done in the scope of a single file, this one too depends on #282 to be truly useful. Requirements like "any package...