-
# 💡 Summary #
The Rego code for Sharepoint policy 3.2 incorrectly produces an N/A when you run with a service principal. I guess the coder thought that the Get-PnPTenant cmdlet does not contain the…
-
now `vuls-opsgenie.rego` contains a very simple template for OpsGenie messages.
we should add more useful details and filters that allows to transform inputs.
eg. severity depends on the result,…
-
I'm currently exploring available Terraform static analysis tools, and stumbled across Terrascan and was wondering if it could be used against a code base that's using Terragrunt and remote backends.
…
-
# 🐛 Summary #
My inaugural run of ScubaGear, I followed the instructions. Initialize-Scuba ran OK except for warning:
`" Unable to download OPA executable. To try manually downloading, see details…
-
Hello,
with the current helm chart is not possible to add a rego policy for filtering vulnerabilities (https://aquasecurity.github.io/trivy/v0.28.1/docs/vulnerability/examples/filter/), seems there…
-
**Description**
We are trying to print error messages when cosign verify-attestation failed as per the rego policy rules.
I have a policy to satisfy my requirement, it’s working from the rego playg…
-
I tested implementation with few rego sensors and get some feedback from heat pump but not correct ones. Here is log information from few minutes test round:
----- 8< -------------------- 8< -…
S4ube updated
10 months ago
-
The following rego
```rego
package test
import future.keywords
allow := input.x if { not input.x }
else := 5
```
incorrectly evaluates to `{"expressions":[{"test":{}}]}`
-
I think it was @johanfylling who suggested that we should have a `style` category rule to enforce ordering of imports, as well as grouping based on the "base path" in the imports. Something along the …
-
Or whatever number makes the most sense. When there are hundreds of violations, it's not a great experience having to scroll over several pages to see them, and even the "compact" view is currently qu…