Skip to content

wasm/extensions: Wasm extension policy. #13526

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.

Sign up for GitHub

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

Merged
mattklein123 merged 1 commit into from
Oct 13, 2020
Merged

wasm/extensions: Wasm extension policy. #13526

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions EXTENSION_POLICY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,19 @@ In the event that the Extension PR author is a sponsoring maintainer and no othe
is available, another maintainer may be enlisted to perform a minimal review for style and common C++
anti-patterns. The Extension PR must still be approved by a non-maintainer reviewer.

## Wasm extensions

Wasm extensions are not allowed in the main envoyproxy/envoy repository unless
part of the Wasm implementation validation. The rationale for this policy:
* Wasm extensions should not depend upon Envoy implementation specifics as
they exist behind a version independent ABI. Hence, there is little value in
qualifying Wasm extensions in the main repository.
* Wasm extensions introduce extensive dependencies via crates, etc. We would
prefer to keep the envoyproxy/envoy repository dependencies minimal, easy
to reason about and maintain.
* We do not implement any core extensions in Wasm and do not plan to in the
medium term.

## Extension stability and security posture

Every extension is expected to be tagged with a `status` and `security_posture` in its
Expand Down