This message was deleted.

Hey @Adrian Patterson 👋 Someone will be with you shortly to answer your question! @Ori Shavit

Update: After some more digging, it is in fact a rego parsing error. I see the following:

'errors': [{'code': 'rego_parse_error', 'message': 'var cannot be used for rule name',

I don't really understand how this is possible since I can run a local OPA server perfectly fine and all tests pass. Either way, sorry for the spam it turned out to be a rego error just as others on here have seen. Maybe a suggestion would be to have some more verbose error handling for the set_policy function and print a message telling the user their rego code/json data is invalid 🙂 Thanks and sorry for the spam again!

Might be different versions of OPA - I think “var” was added in later versions as a reserved keyword. I agree re: better error messages 💜 Would you perhaps be willing to take this on as a PR to contribute ? - the more help the better 💪 CC: @Asaf Cohen, @Ori Shavit

I believe it was because I was defining rules like so:

import future.keywords

allow if {
 # rules here
}

After changing to

allow {
 # rules
}

It works! Must be a version issue. I'll take a look at which OPA version I have locally vs. what OPAL uses. Thanks for the tip! I'll see what I can do for a PR 🙂 Would love to contribute. Thanks to the team for being super responsive & helpful.