-
Notifications
You must be signed in to change notification settings - Fork 561
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
WasmPlugin add VmConfig #2227
WasmPlugin add VmConfig #2227
Conversation
Skipping CI for Draft Pull Request. |
36f32b9
to
2a64590
Compare
2a64590
to
2efcabf
Compare
2efcabf
to
1677940
Compare
release notes will add when implemented in istio repo |
/retest-required |
/test release-notes_api |
6b464d6
to
2ded56d
Compare
2ded56d
to
3bab299
Compare
3bab299
to
bff2ca5
Compare
@bianpengyuan @howardjohn ptal |
7bd9896
to
07d34fb
Compare
blocked by #2235 |
/test gencheck_api |
updated, @howardjohn @bianpengyuan ptal |
// imagePullSecret: private-registry-pull-secret | ||
// phase: AUTHN | ||
// pluginConfig: | ||
// openid_server: authn |
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.
when should a user use pluginConfig vs vmConfig?
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.
vm config is for the runtime configuration (i.e. code written by use), while plugin config is for the plugin (code written by user).
lgtm, I removed @bianpengyuan review since it was stale. @bianpengyuan can you take a look to make sure its good? Thanks! |
202e721
to
393086c
Compare
envoyproxy/envoy#14958 is merged
add
VmConfig
support get env in wasm extensions@bianpengyuan @mathetake PTAL