-
Notifications
You must be signed in to change notification settings - Fork 84
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
deprecated: delete envoy_stream_options #643
Labels
Comments
rebello95
added a commit
that referenced
this issue
Feb 19, 2020
jpsim
pushed a commit
to envoyproxy/envoy
that referenced
this issue
Nov 28, 2022
As of envoyproxy/envoy-mobile#616, this is no longer used or necessary since it's handled by the router. Resolves envoyproxy/envoy-mobile#643. Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
jpsim
pushed a commit
to envoyproxy/envoy
that referenced
this issue
Nov 29, 2022
As of envoyproxy/envoy-mobile#616, this is no longer used or necessary since it's handled by the router. Resolves envoyproxy/envoy-mobile#643. Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
stream options was added in order to configure buffering for retries. This was required when the direct API leveraged the AsyncClient. However, after #616 the option is no longer needed as the Router uses the configured retry policy in the route/and or headers in the stream to determine if retries are enabled and thus if body data has to be buffered.
After #616 merges envoy_stream_options can be removed. Note, for Lyft, that this is a breaking API change so the Apps function calls will have to be updated when the parameter is removed.
The text was updated successfully, but these errors were encountered: