{
  "id": 9220834,
  "title": "When OPA's Bundle Loader Runs Past a `.manifest` Typo",
  "url": "https://urgent.news/2026/09/22/when-opas-bundle-loader-runs-past-a-manifest-typo",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-22T22:53:25.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/whenitruns/when-opas-bundle-loader-runs-past-a-manifest-typo-1d57"
  },
  "original_language": "en",
  "account": "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.",
  "summary": "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…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}