matching: added a new local reply matcher input to distinguish Envoy generated responses#43838
Conversation
|
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
…responses Signed-off-by: Rohit Agrawal <rohit.agrawal@databricks.com>
2e66e09 to
025a41b
Compare
|
/lgtm api |
Signed-off-by: Rohit Agrawal <rohit.agrawal@databricks.com>
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces a new HttpResponseLocalReplyMatchInput to differentiate between local replies generated by Envoy and responses from upstream services. The implementation is clear, correct, and includes comprehensive unit and integration tests that validate the new functionality, especially in conjunction with the custom_response filter. The changes are well-structured and align with existing code patterns, and the documentation and changelog entries are clear. No issues were found during the review.
|
/retest |
…generated responses (envoyproxy#43838) ## Description This PR adds a new local reply matcher input to distinguish Envoy generated local replies from upstream responses. This matcher input returns `true` for local replies and `false` for upstream responses, enabling `custom_response` filter policies to selectively apply only to locally generated error responses. Fix envoyproxy#43811 --- **Commit Message:** matching: added a new local reply matcher input to distinguish Envoy generated responses **Additional Description:** Added a new local reply matcher input to distinguish Envoy generated local replies from upstream responses. **Risk Level:** Low **Testing:** Added Unit + Integration Tests **Docs Changes:** Added **Release Notes:** Added Signed-off-by: Rohit Agrawal <rohit.agrawal@databricks.com> Signed-off-by: bjmask <11672696+bjmask@users.noreply.github.com>
…generated responses (envoyproxy#43838) ## Description This PR adds a new local reply matcher input to distinguish Envoy generated local replies from upstream responses. This matcher input returns `true` for local replies and `false` for upstream responses, enabling `custom_response` filter policies to selectively apply only to locally generated error responses. Fix envoyproxy#43811 --- **Commit Message:** matching: added a new local reply matcher input to distinguish Envoy generated responses **Additional Description:** Added a new local reply matcher input to distinguish Envoy generated local replies from upstream responses. **Risk Level:** Low **Testing:** Added Unit + Integration Tests **Docs Changes:** Added **Release Notes:** Added Signed-off-by: Rohit Agrawal <rohit.agrawal@databricks.com>
Description
This PR adds a new local reply matcher input to distinguish Envoy generated local replies from upstream responses. This matcher input returns
truefor local replies andfalsefor upstream responses, enablingcustom_responsefilter policies to selectively apply only to locally generated error responses.Fix #43811
Commit Message: matching: added a new local reply matcher input to distinguish Envoy generated responses
Additional Description: Added a new local reply matcher input to distinguish Envoy generated local replies from upstream responses.
Risk Level: Low
Testing: Added Unit + Integration Tests
Docs Changes: Added
Release Notes: Added