Patrick East b39b34760e rego: Avoid re-using transactions in compiler ...

Any time we do a compilation in the Rego object (or helpers) we need
to be careful to setup a conflict check that is valid for the current
context (both literal golang ctx and current storage transaction).

This isn't much of a concern if the Rego instance owns the compiler,
but if an external one was provided we need to be careful to update
the conflict check before compiling.

This was already doing the "right thing" when activating bundles, but
for partial evaluation results that were being updated on the compiler
it was not.

Fixes: #2197
Signed-off-by: Patrick East <east.patrick@gmail.com>

2020-04-06 13:54:29 -07:00

..

authorizer

server: Add request headers to authorization input

2019-06-03 07:11:59 -07:00

identifier

server: add authentication based on TLS

2019-01-14 12:57:35 -08:00

testdata

server: add authentication based on TLS

2019-01-14 12:57:35 -08:00

types

server: Add bundles option to /health API

2020-02-07 09:49:41 -05:00

writer

Add Prometheus metrics to the status updates

2019-08-15 15:08:38 -04:00

buffer.go

server: Remove deprecated diagnostic feature

2019-08-06 02:25:09 +09:00

cache_test.go

server: Cache PreparedEvalQuery's for data requests

2019-12-18 11:07:14 -08:00

cache.go

server: Cache PreparedEvalQuery's for data requests

2019-12-18 11:07:14 -08:00

doc.go

Refactor server into separate package

2016-08-08 09:20:24 -07:00

server_test.go

rego: Avoid re-using transactions in compiler

2020-04-06 13:54:29 -07:00

server.go

server: Specify a PartialNamespace for Rego objects

2020-04-06 05:54:03 -07:00