[WIP] feat: migrate from tinygo to go by replacing proxy-wasm-go-sdk#313
Draft
pdefreitas wants to merge 1 commit intocorazawaf:mainfrom
Draft
[WIP] feat: migrate from tinygo to go by replacing proxy-wasm-go-sdk#313pdefreitas wants to merge 1 commit intocorazawaf:mainfrom
pdefreitas wants to merge 1 commit intocorazawaf:mainfrom
Conversation
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
1 participant
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.
Depends on proxy-wasm/proxy-wasm-cpp-host#433 to be merged and updated by Envoy, Istio and other consumers of it.
As PoC to prove feasibility of migration, I've tested locally with envoy v1.36 with custom proxy-wasm-cpp-host and it passes both e2e and go ftw tests.
Performance:
go-ftw tests run with much worse performance even when using wasilibs. The output wasm binary is bigger as well.
tinygo:
go: