-
Notifications
You must be signed in to change notification settings - Fork 575
Virtual Service Direct Response #2407
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
😊 Welcome @sschepens! This is either your first contribution to the Istio api repo, or it's been You can learn more about the Istio working groups, code of conduct, and contributing guidelines Thanks for contributing! Courtesy of your friendly welcome wagon. |
Hi @sschepens. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
eba99f1
to
ad35a3c
Compare
/ok-to-test |
🤔 🐛 You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test? Courtesy of your friendly test nag. |
@ericvn |
It could be that there is a difference in tooling used when running locally vs within the pipeline. I hope to fix that here shortly. |
@ericvn I pushed a commit using the previous image so that CI is happy.
|
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 overall, would like an example on bytes
This reverts commit 293ec72.
|
Added bytes example. I think format binary is ok though, should be ready for merge. |
/retest |
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
Note that the envoy filter has an "unknown security posture" that makes me quite nervous about including this in the API |
@louiscryan I think what you're seeing is the network filter (which is not used for HTTP) and not the direct_response of the router filter. The router filter has a known security posture. |
// - match: | ||
// - uri: | ||
// exact: /v1/getProductRatings | ||
// directResponse: |
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.
As mentioned in the Envoy docs its good practice to recommend setting response headers, particularly content-type. Can you add that to one of the examples.
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.
sure, i can add
Ah ok, thanks for clarifying |
@louiscryan added an example with headers |
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
// directResponse: | ||
// status: 503 | ||
// body: | ||
// string: "unknown error" |
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.
is this right?
Fixes istio/istio#29264