-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow opt-in with wasm engine #650
Comments
Started playing with this a bit here -- but I've stumbled upon the inter query builtin cache, and I'm currently not sure how that's handled in Wasm 🤔 🔍 |
srenatus
referenced
this issue
in srenatus/opa
Aug 9, 2021
Found when looking into #3716. With this change, multiple calls to a wasm-backed eval that uses http.send would re-use the results (if caching permits). Signed-off-by: Stephan Renatus <[email protected]>
This was referenced Aug 9, 2021
srenatus
referenced
this issue
in open-policy-agent/opa
Aug 9, 2021
Found when looking into #3716. With this change, multiple calls to a wasm-backed eval that uses http.send would re-use the results (if caching permits). Signed-off-by: Stephan Renatus <[email protected]>
ℹ️ this will now need to account for open-policy-agent/opa#3708 |
jgchn
referenced
this issue
in jgchn/opa
Aug 20, 2021
) Found when looking into #3716. With this change, multiple calls to a wasm-backed eval that uses http.send would re-use the results (if caching permits). Signed-off-by: Stephan Renatus <[email protected]>
srenatus
changed the title
opa-envoy-plugin: all opt-in with wasm engine
opa-envoy-plugin: allow opt-in with wasm engine
Aug 27, 2021
srenatus
referenced
this issue
in srenatus/opa-istio-plugin
Sep 13, 2021
This turns the simple grpc tests scenario into a matrix test for both evaluation variants. Fixes open-policy-agent/opa#3716. Signed-off-by: Stephan Renatus <[email protected]>
srenatus
referenced
this issue
in srenatus/opa-istio-plugin
Sep 27, 2021
This turns the simple grpc tests scenario into a matrix test for both evaluation variants. Fixes open-policy-agent/opa#3716. Signed-off-by: Stephan Renatus <[email protected]>
dolevf
referenced
this issue
in dolevf/opa
Nov 4, 2021
) Found when looking into #3716. With this change, multiple calls to a wasm-backed eval that uses http.send would re-use the results (if caching permits). Signed-off-by: Stephan Renatus <[email protected]> Signed-off-by: Dolev Farhi <[email protected]>
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. |
srenatus
changed the title
opa-envoy-plugin: allow opt-in with wasm engine
allow opt-in with wasm engine
Jan 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, the opa-envoy-plugin is configured to use exactly one query, and it's caching the prepare eval state. It should be possible to use wasm instead of the rego target.
It may be worthwhile to re-run some benchmarks to compare rego vs wasm in the envoy scenario.
💭 Note that this has nothing to do with running the wasm modules that OPA can compile a policy to in envoy directly. While very neat, that's another issue (#3235). This one should be a much lower-hanging fruit.
The text was updated successfully, but these errors were encountered: