-
Notifications
You must be signed in to change notification settings - Fork 360
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
api: ext-proc processing mode #3171
Conversation
Signed-off-by: Guy Daich <guy.daich@sap.com>
ae8c6b2
to
844558b
Compare
/retest |
/retest |
1 similar comment
/retest |
@guydc sorry, linter works as expected now, can you fix it? |
1 similar comment
@guydc sorry, linter works as expected now, can you fix it? |
/retest |
/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
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
api/v1alpha1/ext_proc_types.go
Outdated
type ExtProcBodyProcessingMode string | ||
|
||
const ( | ||
StreamedExtProcBodyProcessingMode ExtProcBodyProcessingMode = "Streamed" |
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.
Could we add comments for each mode? This way they can show in the generated API docs.
Signed-off-by: Guy Daich <guy.daich@sap.com>
Minor/non-blocking comment on naming:
|
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 thanks !
yeah this API field is doing two things
can't think of a better name, so lets go ahead with the envoy specific name, since this feature is completely tied to envoy |
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, thanks.
What this PR does / why we need it:
Allows users to define how request and response header/body are processed by exteral processing service.
By default, nothing is sent to the external processor. If an empty request/response struct is defined, headers of request/response are sent. If the body attribute is configured, the body is processed according to the defined processing mode (Stream, Buffer, BufferPartial).
Which issue(s) this PR fixes:
xref: #3170