Ashutosh Narkar

I was suggesting you create a draft PR in https://github.com/open-policy-agent/opa with your changes and then you can get the Netlify preview of the docs.

[Resource Utilization](https://www.openpolicyagent.org/docs/latest/policy-performance/#resource-utilization) would be a good place to mention this.

Closing this in favor of https://github.com/open-policy-agent/opa/issues/4744

Currently the entire request object is used as the cache key. It would be interesting to look into how that behavior can be controlled via a new param maybe. So...

@rudrakhp if you'd like to contribute this feature feel free to do so.

The proposed `rego.Data` similar to `rego.Load`, `rego.LoadBundle` and `rego.ParsedBundle` would require a transaction to be passed as well. Then should be just a write call on the store as part...

I was referring to [this](https://sourcegraph.com/github.com/open-policy-agent/opa@db3b016f98763c277c625a3431f51da32c3eef78/-/blob/rego/rego.go?L969) comment where you set the store and that this would apply to `rego.Data` as well.

But then this would make it different than `rego.ParsedBundle` for instance since in the `rego.ParsedBundle` case you'd actually write the bundle contents to the store. But that's not how you...

Thanks for the contribution @tsidebottom. FYI we've added some comments on https://github.com/open-policy-agent/opa/issues/6559 about the proposed feature including the latest one [here](https://github.com/open-policy-agent/opa/issues/6559#issuecomment-2042333865). It would be helpful to identify alternate ways of...

[This](https://github.com/open-policy-agent/opa/blob/main/topdown/http.go#L1335) method handles the response processing which would need to be updated I think. Feel free to submit a PR if you'd like. Thanks.