Package Exports
- @open-policy-agent/opa-wasm
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@open-policy-agent/opa-wasm) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Work in Progress -- Contributions welcome!!
Open Policy Agent WebAssemby NPM Module
This is the source for the @open-policy-agent/opa-wasm NPM module which is a small SDK for using WebAssembly (wasm) compiled Open Policy Agent Rego policies.
Getting Started
Install the module
npm install @open-policy-agent/opa-wasm Usage
There are only a couple of steps required to start evaluating the policy.
Import the module
const { loadPolicy } = require("@open-policy-agent/opa-wasm");Load the policy
loadPolicy(policyWasm)The loadPolicy function returns a Promise with the loaded policy.
Typically this means loading it in an async function like:
const policy = await loadPolicy(policyWasm)Or something like:
loadPolicy(policyWasm).then(policy => {
// evaluate or save the policy
}, error => {
console.error("Failed to load policy: " + error)
})The policyWasm needs to be either the raw byte array of
the compiled policy Wasm file, or a WebAssembly module.
For example:
const fs = require('fs');
const policyWasm = fs.readFileSync('policy.wasm');Alternatively the bytes can be pulled in remotely from a fetch or in some
cases (like CloudFlare Workers) the Wasm binary can be loaded directly into the
javascript context through external APIs.
Evaluate the Policy
The loaded policy object returned from loadPolicy() has a couple of important
APIs for policy evaluation:
setData(obj) -- Provide an external data document for policy evaluation. Requires a JSON serializable object.
evaluate(input) -- Evaluates the policy using any loaded data and the supplied input document.
The input parameter must be a JSON string.
Example:
input = '{"path": "/", "role": "admin"}';
loadPolicy(policyWasm).then(policy => {
resultSet = policy.evaluate(input);
if (resultSet == null) {
console.error("evaluation error")
}
if (resultSet.length == 0) {
console.log("undefined")
}
console.log("allowed = " + allowed[0].result);
}).catch( error => {
console.error("Failed to load policy: ", error);
})For any
opa buildcreated WASM binaries the result set, when defined, will contain aresultkey with the value of the compiled entrypoint. See https://www.openpolicyagent.org/docs/latest/wasm/ for more details.
Writing the policy
See https://www.openpolicyagent.org/docs/latest/how-do-i-write-policies/
Compiling the policy
Either use the Compile REST API or opa build CLI tool.
For example, with OPA v0.20.5+:
opa build -t wasm -e 'example/allow' example.regoWhich is compiling the example.rego policy file with the result set to
data.example.allow. The result will be an OPA bundle with the policy.wasm
binary included. See ./examples for a more comprehensive example.
See opa build --help for more details.