policy

Expected Behavior

At https://github.com/open-policy-agent/opa/blob/main/bundle/bundle_test.go#L31, the result of function Equal not used:

m.rootSet().Equal(stringSet{"x/y": struct{}{}, "y/z": struct{}{}})

while this function has no side effect:

func (ss stringSet) Equal(other stringSet) bool 

Is your feature request related to a problem? Please describe.
Installation script supports only x86_64 architecture. 386 and arm64 are not supported.

Describe the solution you'd like
Detect the machine's architecture and download the relevant release in the install script

Additional context
the relevant file that should be changed should be install.sh and `windows_install.p

https://github.com/project-oak/oak/blob/4f2063aea9fc8afa123617d1bf9e518b58469562/oak_functions/examples/weather_lookup/module/src/tests.rs#L196

I think we should avoid using "real" randomness in tests, and especially in benchmarks, which are expected to converge. So perhaps we should consider a fixed-seed RNG (see https://docs.rs/rand/0.8.4/rand/trait.SeedableRng.html#tymethod.from_seed ).

What are fetch providers?

FetchProviders are the components OPAL uses to fetch data from sources on demand.

Fetch providers are designed to be extendable, and you can easily create more fetch providers to enable OPAL to fetch data from your own unique sources (e.g. a SaaS service, a new DB, your own proprietary solution, ...)

[We have a guide on how to write new fetch providers](https:/

What would you like to be added:

The references to the MAGTAPE_TLS_SECRET environment variable should be removed and the documentation for the "Bring Your Own Cert" (BYOC) model needs to be corrected.

The BYOC model requires an annotation on the magtape-tls secret. Details are within the magtape-init code