Stephan Renatus

> 3. I don't think we can get away with not suporting sets. It's just such a common data type in Rego, that we'll need at least some way to...

> 4. Since you mentioned you only considered custom builtin functions here, is there something making it difficult to leverage the same capability to deploy e.g. a decision logger plugin?...

That's a good point, btw, custom builtins provided via wasm modules need some kind of type annotation.

Can you please elaborate on your expectations? Should the request ID header become part of the response, or part of the open telemetry spans, or be used in decision logs...?...

Ah. So concretely, you're expecting the header to be sent along with `http.send` calls to remote services.

So we'd basically make the default config configurable? The rationale is clear, let's try to fix that.

What I meant is that some local config would always augment (override?) the config that comes in via discovery. I think we're talking about the same thing 🤞

So I myself keep forgetting that ☝️ this is a thing -- discovery can be a policy. ✨ So that policy would allow the OPA instance to determine the proper...

``` template: docs/ecosystem.html.html:158:37: executing "main" at : error calling partial: "/opt/build/repo/docs/website/layouts/partials/docs/integration-org-link.html:1:12": execute of template failed: template: partials/docs/integration-org-link.html:1:12: executing "partials/docs/integration-org-link.html" at : error calling index: index of untyped nil ``` this...

Feel free to reopen when you find the time.