Skip to content

matching: added a new local reply matcher input to distinguish Envoy generated responses#43838

Merged
yanavlasov merged 5 commits intoenvoyproxy:mainfrom
agrawroh:feat-local-reply-matcher
Mar 11, 2026
Merged

matching: added a new local reply matcher input to distinguish Envoy generated responses#43838
yanavlasov merged 5 commits intoenvoyproxy:mainfrom
agrawroh:feat-local-reply-matcher

Conversation

@agrawroh
Copy link
Copy Markdown
Member

@agrawroh agrawroh commented Mar 7, 2026

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 #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

@repokitteh-read-only
Copy link
Copy Markdown

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to (api/envoy/|docs/root/api-docs/).
envoyproxy/api-shepherds assignee is @mattklein123
CC @envoyproxy/api-watchers: FYI only for changes made to (api/envoy/|docs/root/api-docs/).

🐱

Caused by: #43838 was opened by agrawroh.

see: more, trace.

…responses

Signed-off-by: Rohit Agrawal <rohit.agrawal@databricks.com>
@agrawroh agrawroh force-pushed the feat-local-reply-matcher branch from 2e66e09 to 025a41b Compare March 7, 2026 22:04
@wbpcode
Copy link
Copy Markdown
Member

wbpcode commented Mar 8, 2026

/lgtm api

@repokitteh-read-only repokitteh-read-only bot removed the api label Mar 8, 2026
@yanavlasov
Copy link
Copy Markdown
Contributor

/gemini review

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@yanavlasov yanavlasov enabled auto-merge (squash) March 11, 2026 18:24
@agrawroh
Copy link
Copy Markdown
Member Author

/retest

@yanavlasov yanavlasov merged commit 178727b into envoyproxy:main Mar 11, 2026
28 of 29 checks passed
bmjask pushed a commit to bmjask/envoy that referenced this pull request Mar 14, 2026
…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>
fishcakez pushed a commit to fishcakez/envoy that referenced this pull request Mar 25, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a local-reply matcher input for custom_response policies

4 participants