Add routeId to filterContext#3856
Merged
MustafaSaber merged 2 commits intozalando:masterfrom Feb 7, 2026
Merged
Conversation
Filters can have now access to the specific route ID that was triggered for the request. Signed-off-by: Xavi Ivars <xavi.ivars@gmail.com>
|
Cannot start a pipeline due to: Click on pipeline status check Details link below for more information. |
szuecs
approved these changes
Feb 4, 2026
Signed-off-by: Xavi Ivars <xavi.ivars@gmail.com>
|
Cannot start a pipeline due to: Click on pipeline status check Details link below for more information. |
szuecs
approved these changes
Feb 7, 2026
MustafaSaber
approved these changes
Feb 7, 2026
This was referenced Feb 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This MR exposes the route ID to
filterContext.Over the past few years, we've seen many instances where it could have been handy to know the route that was triggered for a specific request: we have predicates that match based on A/B testing, or other input (headers/cookies), and there may be multiple routes that end up in the same origin.
Being able to track (and potentially log, or apply filters based on) the route ID would be extremely helpful for us.
Slack conversation: https://gophers.slack.com/archives/C82Q5JNH5/p1755799907005649