-
## What is the underlying problem you're trying to solve?
I have a use case where I need to use a user-defined Rego function from another policy that is part of a policy library. However, I don't…
-
It seems the timers we're using through the Go standard library are not high enough resolution for some the operations that we keep track of. This results in metrics being returned from OPA or emitted…
-
Working on #1131 I hit some severe performance issues around aggregate rule violations, frequently leading to the language server to either hang, or heavily tax the CPU. The reason for this is that ag…
-
**Describe the bug:**
When starting the servo shell with the default URL, I noticed a pipeline that keeps animating, which causes the servo shell to keep polling and results in high CPU usage.
Addin…
-
From a discussion with @klauern in the OPA Slack, and from my own experiences working with tests in policy repositories, we think the OPA test runner could be improved for this scenario. Running unit …
-
```rego
package test
p {
resp := true
g(true) with f as resp
}
g(x) = f(x)
f(false) = true
```
opa eval -d t.rego data.test.p | -t rego | -t wasm
---|---|---
result | true | undefined
…
-
Is there a list somewhere with current implementations? so far I've found https://github.com/google/cel-cpp and https://github.com/google/cel-go.
Also, it will be very useful for newcomers like me…
-
#### Introduction:
Proposing the integration of the Witness Policy Tool into Witness, including the addition of a new command: `witness policy`. This integration aims to streamline processes and impr…
-
## Expected Behavior
a.rego
```rego
package root.a
import data.root
rule_a = x {
x = {
"b": root.b,
}
}
```
a_test.rego
```rego
package root.a
test_rule_a {
rule_a == …
-
#### Current Behavior
Meshery's highly dynamic infrastructure configuration capabilities require real-time evaluation of complex policies. Policies of various types and with a high number of paramet…