Johan Fylling
Johan Fylling
Rego allows rules to be declared on the same line: ```rego package test foo(x) {x == 2} bar {true} baz := 1 ``` The policy ```rego package test p(x) if...
We should add suggestions for package related subjects: * Naming convention * How to organize support/helper packages * When to split a policy into multiple files * How folder structure...
Implements: #6578
When OPA builds a bundle, the Rego version (0.x or 1.0) should be included as a manifest attribute. When the version of the contained Rego is advertised by the bundle...
When building a bundle from the following module with `opa build -O1`: ```rego package test import rego.v1 # METADATA # entrypoint: true p if { input.x == 1 } ```...
The `http.send()` and `net.lookup_ip_addr()` built-in functions can be allow-listed by host through the `allow_net` Capabilities param. This feature is, however, limited to the `eval` command. If capabilities could also be...
If a policy has two `METADATA` blocks declared back-to-back, with no empty lines in-between, e.g.: ```rego package play # METADATA # title: Ps # scope: document # METADATA # title:...
In the docs, a section should be added where, for each deprecated built-in, an alternative function call or snippet of Rego is described. When running `opa check` and `opa fmt`...
A danger of using custom annotations not organized into the `custom` annotation in a `METADATA` comment block is that your policy is vulnerable to future OPA updates. E.g. the following...
Given the policy: ```rego package test import future.keywords.if p if { true } ``` and a modified capabilities file, where we've removed the `if` keyword: ```json { "builtins": [ {...