When OPA's Bundle Loader Runs Past a `.manifest` Typo
In bundle mode, a one-character .manifest key typo ( rego_verison for rego_version ) draws no diagnostic that names the key; the failure can surface as rego_parse_error pointing at your .rego — OPA v1.20.1 When It Runs — Run Report #RR03 · Testing what infrastructure actually does. Provider · Component: OPA (Open Policy Agent) · bundle .manifest loading — unknown top-level keys and rego_version…
When the OPA bundle loader encounters a typo in the `.manifest` key, such as `rego_verison` instead of the correct `rego_version`, it fails to generate a diagnostic specifically naming the key. This can lead to the failure manifesting as a `rego_parse_error: if` keyword is required before rule body, with the error pointer directed at the `.rego` source file.
However, if the mistyped key is present in the sibling `config.yaml` file, an explicit warning about an unknown configuration option has been displayed since version 1.19.0 of OPA.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
