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
when running regal fix [[path] --disable-all/-D or regal fix [path] --disable [rule] the use-rego-v1 rule will always be ran even if you try to disable it
The text was updated successfully, but these errors were encountered:
Either way, if we intend to keep it this way we should document that. Are there any reasons you can't use import rego.v1?
OPA 1.0 is like a month or so away, so you'll want to prepare for that now :)
Aah yeah it is, didn't look at the code to verify. It would be nice if it was shown in the docs or the regal fix --help prompt that rego-v1 will be applied as default, and with no option to disable.
There is no reason we cant use it, but I get some pushback if I change other application teams rego policies, but with V1 looming over us I can emphasise the importance.
Came across this while enabling the 0.27 rules, but anyhow I don't wanna do both rego-v1 and the directory-package-mismatch rules on our repo at the same time. But I'll just do v1 first, and then directory structure afterwards in a separate pull request.
when running
regal fix [[path] --disable-all/-D
orregal fix [path] --disable [rule]
the use-rego-v1 rule will always be ran even if you try to disable itThe text was updated successfully, but these errors were encountered: