Open dxh9845 opened 1 month ago
Thanks for reporting this 👍 I haven't looked into it, but it sounds somewhat related to #6529 ... at least in how they both relate to a different compilation mode messing with metadata annotations. Have you had a chance to look at the files in the bundle?
Here you go:
{
"revision": "",
"roots": [
"main",
"meta",
"some_data"
],
"wasm": [
{
"entrypoint": "main/zone_alias",
"module": "/policy.wasm",
"annotations": [
{
"entrypoint": true,
"related_resources": [
{
"description": "Some description",
"ref": "https://google.com"
}
],
"scope": "rule"
}
]
},
{
"entrypoint": "meta/foo",
"module": "/policy.wasm",
"annotations": [
{
"entrypoint": true,
"scope": "rule"
}
]
}
]
}
package main
import data.main.zone_alias
import data.meta.foo
Ah, thanks! No, this looks like a different issue then, as the metadata annotation is in the manifest. And hopefully easier to resolve 🙂
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue.
Short description
Running
opa inspect
on a built WASM bundle that has the followingrelated_resources
annotation:Will fail with the following message:
Steps To Reproduce
make fail
to build the bundle and see the failure:Expected behavior
OPA can inspect the built WASM bundle without an error.
Additional context
This works for OPA packages built for
rego
. However, the WASM implementation seemingly cannot handle