The Rego compiler supports strict mode, where additional constraints and safety checks are enforced during compilation.
Compiler rules that will be enforced by future versions of OPA, but will be a breaking change once introduced, are incubated in strict mode.
This creates an opportunity for users to verify that their policies are compatible with the next version of OPA before upgrading.
Compiler Strict mode is supported by the check command, and can be enabled through the -S flag.
-S, --strict enable compiler strict mode
Strict Mode Constraints and Checks
| Name | Description | Enforced by default in OPA version |
|---|---|---|
| Duplicate imports | Duplicate imports, where one import shadows another, are prohibited. | 1.0 |
| Unused local assignments | Unused arguments or assignments local to a rule, function or comprehension are prohibited | 1.0 |
| Unused imports | Unused imports are prohibited. | 1.0 |
input and data reserved keywords | input and data are reserved keywords, and may not be used as names for rules and variable assignment. | 1.0 |
| Use of deprecated built-ins | Use of deprecated functions is prohibited, and these will be removed in OPA 1.0. Deprecated built-in functions: any, all, re_match, net.cidr_overlap, set_diff, cast_array, cast_set, cast_string, cast_boolean, cast_null, cast_object | 1.0 |
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.