Anders Eknert

Sure: ```rego package p default x(_) := "default" x_is := x(input.undefined) ``` ```shell $ opa eval -f pretty -d p.rego data.p.x_is undefined ``` The root cause being the same as...

@itayhac 👍 If you're able to share your actual policy where this is problematic, it could be a good test case for the fix.

Sounds good. The reason I'm asking is that while the problem exposed by the example policy above is real, referencing an array without actually using it.. I guess there are...

@mahi072 sure thing! Go right ahead, and holler out if you need any help.

This is the page where it's mentioned: https://www.openpolicyagent.org/docs/latest/monitoring/#prometheus Which maps to this file in the repo: https://raw.githubusercontent.com/open-policy-agent/opa/main/docs/content/monitoring.md

While they aren't synchronized, the "synchronization" in this case happens via the annotation, which seems to cause a race condition. But yes, ideas / fixes most definitely welcome :)

I really like @charlieegan3's idea of having an alternative mode for kube-mgmt, where it acts as a bundle server for any number of OPAs. You'd still want to run more...

I'm afraid I don't remember the details of the PREFIXED topic type. @scholzj might be able to answer. https://play.openpolicyagent.org/p/Fm49HlM0e8

Hi Thor! Yeah, that seems like a valid request. I wonder what the best approach would be for achieving that 🤔 I guess we could defer to a different serializer...

Yeah, doing JWT validation in OPA, and policy decisions based on claims makes perfect sense. @scholzj any idea about how to best go on about allowing this?