Thanks for sharing the OPAL v0.9.0 release announcement! This is a significant update that brings OPA v1 support to OPAL. The key change is that OPAL v0.9.x now ships with OPA v1 by default (1) . To ensure a smooth transition, OPAL v0.9.x enables v0 compatibility mode automatically by setting

OPAL_OPA_V0_COMPAT=true

(1) (2) . This means your existing OPA v0 policies will continue to work without immediate changes (1) . For the eOPA variant mentioned in the release, you can use the new Docker image:

service:
 opal_client:
 image: permitio/opal-client-eopa:latest

(3) Important Migration Notes In OPAL v0.10.0, the

OPAL_OPA_V0_COMPAT

setting will be unconfigured (effectively

false

) by default (1) (2) . To prepare for this: 1. Test your current policies with v0 compatibility enabled (which is the default in v0.9.x) (1) 2. Migrate your Rego policies from OPA v0 to v1 syntax - key changes include adding

.v1

suffix to package declarations, replacing

=

with

:=

for assignments, and updating guard syntax 3. Use the migration utilities:

opa fmt --rego-v1

to transition your policies and

opa check --rego-v1

to verify compatibility (4) The v0 compatibility mode is controlled by the

OPAL_OPA_V0_COMPAT

setting or through `OPAL_INLINE_OPA_CONFIG`:

export OPAL_OPA_V0_COMPAT=true

(1) If either

OPAL_OPA_V0_COMPAT

or

OPAL_INLINE_OPA_CONFIG.v0_compatible

is

true

, the

--v0-compatible

flag will be added to OPA .

To learn more, see the sources I considered: [[1] OPA Version Migration Guide](https://docs.opal.ac/tutorials/opa-version-migration) [[2] OPAL Configuration Guide | OPAL](https://docs.opal.ac/getting-started/configuration) [[3] OPAL Client](https://docs.opal.ac/getting-started/quickstart/docker-compose-config/opal-client) [[4] OPA v1 is Almost Out! Here’s What You Need to Know](https://www.permit.io/blog/whats-new-on-opa-v1)