Anders Eknert
Anders Eknert
Interesting. I don't recall us having made any changes in that code recently. I wonder if it could be some dependency that changed? Oh well, I guess we'll find out...
Hi there! That schema is only checked for the `system.authz` package, which is used for [authentication/authorization](https://www.openpolicyagent.org/docs/latest/security/#authentication-and-authorization) policies protecting OPA's own REST API. Using that package name for other purposes is...
That's interesting, and certainly a reasonable thing to do. I guess the workaround is to disable the schema check like you do alrrady, but I wonder what a better solution...
@garethahealy huh, yeah that looks like a regression in OPA to me. ``` have: "resource" ... want (one of): [... "resource" ...] ``` Mysterious. As far as I'm aware, the...
Yeah, removing that annotation should fix the issue, as the schema was never there to begin with. It's still a regression in OPA, so thanks for reporting that! But I'm...
This should apply to `else` clauses as well: ```rego yes if { user == "joe" } else if { user == "joe" # more conditions } ``` So we'll probably...
As @srenatus found some time back, the caching of numbers in OPA doesn't work as it was expected. Perhaps this issue would be less relevant if it did, and if...
Coming back to this, I think it's too small to motivate a rule of its own. However, perhaps we could have a rule collect smaller optimizations within the scope of...
Rule name `builtin-nitpicks`? :)
With numbers now interned in OPA, there is no longer a need for this 🎉