-
Notifications
You must be signed in to change notification settings - Fork 73
Configuration canary for the second or further plugins. #289
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
Conversation
a68b9ac
to
0da9fd0
Compare
@mathetake @PiotrSikora Friendly ping. |
Can you add tests? Also, the recent issue was a single plugin with multiple configurations (one valid, one invalid), but this is talking about multiple plugins, so it's unclear which case you are trying to address. |
I thought that the multiple filters with the same WasmVM was problematic: envoyproxy/envoy#20843 (comment) In my understanding, |
That's the issue with different instances of the same Wasm plugin (i.e. when same was plugin is started with different plugin configuration). However, #175 (which this PR supposedly resolves) is about multiple Wasm plugins linked in the same Wasm module, which I don't belive this fixes. |
Oh.. "multiple Wasm plugin" means a kind of multiple type? (like network, http, bootstrap) According to #175 (comment), #175 seems to be about that "canary" is not applied to the second plugin instance when |
da5fba7
to
73caefd
Compare
@ingwonsong you need to add rule to build @chaoqin-li1123 @mpwarres could you do the first review pass? Thank you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ingwonsong could you update Proxy-Wasm C++ SDK to latest as part of this PR?
Signed-off-by: Ingwon Song <igsong@google.com>
Signed-off-by: Ingwon Song <igsong@google.com>
Signed-off-by: Ingwon Song <igsong@google.com>
Signed-off-by: Ingwon Song <igsong@google.com>
Signed-off-by: Ingwon Song <igsong@google.com>
b01440d
to
0b7141a
Compare
Signed-off-by: Ingwon Song <igsong@google.com>
0b7141a
to
b361a81
Compare
Signed-off-by: Ingwon Song <igsong@google.com>
Done. |
Done, too. |
Signed-off-by: Ingwon Song <igsong@google.com>
2575f73
to
a28ee34
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG, thanks!
@PiotrSikora Wam reminder. :) |
Signed-off-by: Ingwon Song <igsong@google.com>
70506c9
to
ff3d16a
Compare
…tion Signed-off-by: Ingwon Song <igsong@google.com>
65fea82
to
f011993
Compare
…t_data Signed-off-by: Ingwon Song <igsong@google.com>
Signed-off-by: Ingwon Song <igsong@google.com>
Signed-off-by: Ingwon Song <igsong@google.com>
7ba877e
to
d10641e
Compare
@PiotrSikora Can you take a look once again? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, with a few small comments/nits.
Signed-off-by: Ingwon Song <igsong@google.com>
Signed-off-by: Ingwon Song <igsong@google.com>
Signed-off-by: Ingwon Song <igsong@google.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All three YamlLoadFromFileWasmInvalidConfig
tests in Envoy are failing because of this change, which is a bit unexpected. Could you take a look?
Ideally, you would open a draft PR in Envoy pointing to this unmerged branch.
Sure. will take a look |
Can you check out the behavioral difference in the fixed envoy test cases? TL;DR - now we always apply canary, so the creation of FilterConfig or AccessLog should raise the exception always when the invalid config is configured. |
Signed-off-by: Ingwon Song <igsong@google.com>
47d0cab
to
0bd8418
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Fixes proxy-wasm#175. Signed-off-by: Ingwon Song <igsong@google.com>
Fixes: #175
Applying Configuration Canary for second or further plugin.
In #175, there are some discussion about 1) needs of optimization for multiple plugins, and 2) the initialization in the main thread.
But, before making such optimization, this PR proposes to solve the issue itself because it seems to be critical in terms of stability.