Proxy-WASM configuration protos.#9256
Conversation
Signed-off-by: John Plevyak <jplevyak@gmail.com>
htuch
left a comment
There was a problem hiding this comment.
Thanks for the split. I have a lot of feedback around readability; it's important to keep in mind that these are the docs that end users of Envoy see in https://www.envoyproxy.io/docs/envoy/latest/api/api, so we have really high standards around making them self contained, understandable by average Envoy users and as context free as possible.
/wait
| // multiple filters/services are handled by the same vm_id and root_id and for logging/debugging. | ||
| string name = 1; | ||
|
|
||
| // A unique ID for a set of filters/services in a VM which will share a RootContext and Contexts |
There was a problem hiding this comment.
All docs in the API either should be consumable standalone or should have :ref: to something that explains concepts. At this point, the reader has no idea about root context or event contexts.
There was a problem hiding this comment.
@PiotrSikora will be adding the ABI doc and we will reference it here.
There was a problem hiding this comment.
I would prefer that the ABI doc lands first or we keep track with some annotations of every place we're missing these links.
There was a problem hiding this comment.
@PiotrSikora Please attach ABI doc here.
| // The Wasm runtime type (see source/extensions/common/wasm/well_known_names.h). | ||
| string runtime = 2; | ||
|
|
||
| // The Wasm code that Envoy will execute. |
There was a problem hiding this comment.
I think we need a WASM section in the Envoy architecture intro or configuration docs that we link to that explains things like file format etc.
There was a problem hiding this comment.
@PiotrSikora can we push some of the ABI/docs to the envoyproxy/envoy repo?
mattklein123
left a comment
There was a problem hiding this comment.
Thanks will take another pass once the initial set of comments are addressed.
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
mattklein123
left a comment
There was a problem hiding this comment.
Thanks, at a high level this looks good, but I think to review this there needs to be either a high level arch overview doc, or some other doc that succinctly describes the proposed architecture re: root contexts, etc. If there is a short gdoc we can read for now prior to merging into arch overview that's fine, but please provide that and then we can move forward with this.
/wait
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
|
Any suggestions for how to debug the CI issues. For some reason, despite producing titanic amounts of output, the one thing which is singularly missing is the actual error which caused the CI build to fail. For example, envoy-linux (format) claims that there is a formatting error, but doesn't provide any error message. When I run the tests locally everything passes. Any suggestions? |
…m-upstream-protos
|
The CI formatting error "suggestion" is to delete the files that this PR adds. Needless to say not very helpful. Any suggestions? |
|
#9358 discusses the filter name issue |
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
mattklein123
left a comment
There was a problem hiding this comment.
LGTM, thanks. Will defer to @htuch for final approval/merge.
Signed-off-by: John Plevyak <jplevyak@gmail.com>
htuch
left a comment
There was a problem hiding this comment.
LGTM other than remaining threads. If you really want to reflect that this is still alpha, we should make this v4alpha for the latest API version.
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
…m-upstream-protos Signed-off-by: John Plevyak <jplevyak@gmail.com>
|
RE: Warning for "allow_precompiled", I changed it, but I would say that nobody should be loading a wasm plugin from an untrusted source in any case if for no other reason than the existing ABI is sufficiently powerful to cause trouble without loading arbitrary code. |
Signed-off-by: John Plevyak <jplevyak@gmail.com>
|
Please merge master. I think this will need some doc updates for v3. /wait |
…m-upstream-protos
|
I merged master. What doc updates are you thinking? |
I would have thought that the docs you added in the api-v2 tree would need replicating in the api-v3 tree. I'm not sure why it's not failing due to RST not being present in the tree. In a any case, if it's passing the build we can merge now and sort it out later. cc @htuch |
Signed-off-by: John Plevyak jplevyak@gmail.com
For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description: Proxy_WASM configuration protos.
Risk Level: Low
Testing: N/A
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]