Patrick East

After a quick review of the WASM stuff in OPA it seems like maybe the SDK wouldn't be able to distinguish between the like OPA builtins and a custom one....

IMO we should probably update to support returning a 308 (307 might be appropriate.. but saying its permanent makes more sense IMO, clients don't need to like re-check.. they should...

We discussed this a bit at the OPA weekly meeting (notes https://docs.google.com/document/d/1v6l2gmkRKAn5UIg3V2QdeeCcXMElxsNzEzDkVlWDVg8/edit#heading=h.2ymp0280bora) The conclusion was that we will _not_ change the return code for the `v1` API's. When we make...

@anderseknert sorry for the delay! Its mostly hypothetical.. at some point we'll nudge OPA to v1.x.x and we'll have some flexibility to make backwards incompatible changes (there's an issue label...

You guys make some excellent points. I'm happy to close this out if the consensus is that it is working as expected. I tend to disagree that a compile error...

@mingfang is there a specific example or policy in the library that is missing this? Any more details would be helpful.

> I think a practical solution would be some file naming convention, for example, if I'm evaluating mypolicy.rego the extension can look for a file called input.mypolicy.json or mypolicy.input.json or...