Added feature for loading a custom WASI policy engine as a plugin from a shared library - #2
Open
cdanger wants to merge 1 commit into
Conversation
…n from an external shared library
Michielvk
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an optional CLI option
--policy-engine(as a complement to--policy) that enables Wasmtime to load a custom policy engine from a shared library as a plugin (e.g. THS WASI PEP in ELASTIC Project), i.e. without modifying Wasmtime code. A policy engine in this case is a library responsible for configuring the WASI capabilities, using the--policyargument as initial policy (if one is specified) and/or an external policy decision point for more dynamic policy enforcement. If no--policy-engineis specified, the--policyargument is used like before.