OPA WASM build does not preserve data namespace from folder structure (works in OPA server bundle)

[pkkhokhar]

We are using OPA v0.65.

Our policies are organized in folders, each containing a Rego file and a static data.json. When creating a bundle for the OPA server, the folder structure is preserved and becomes part of the data namespace, so imports like data.abc.data.jsonkey work as expected.

However, when building WASM policies, the same structure is not preserved, and the data appears at the root (data.jsonkey) instead.

wasm build command
opa build -t wasm -e test/entry/point/authorize policies/abc/abc_policy.rego policies/abc/data/data.json -o abc.tar.gz

Example structure

policies/
abc/
abc_policy.rego
data/
data.json
abc2/
abc2_policy.rego
data/
data.json

Issue

1. This works when loading a single bundle into the OPA server for all the policies.
2. In WASM, the policy expects data.jsonkey instead of data.abc.data.jsonkey.

Questions

1. Is it possible to preserve the folder-based data namespace when building WASM?
2. If not, what is the recommended way to structure policies and data so the same Rego code works for both OPA server bundles and WASM?
3. What is the best long-term approach going forward?

[srenatus]

Hey! Thanks for raising this.

First and foremost, OPA v0.65.0 is years old by now -- please upgrade. You're missing out on loads of new features, performance improvements and bug fixes.

About the issue, can you try building your wasm bundle in a different way? Try this, please:

opa build -t wasm  -e test/entry/point/authorize  -b policies  -o abc.tar.gz

[pkkhokhar]

Thanks, this helps