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
[TT-1475] respect ignored paths in CoProcessMiddleware #3452
Conversation
This is initial test for checking if we have ingore plugin enabled
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.
Looks good, shouldn't break any existing functionality.
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
/release to release-3 |
Working on it! Note that it can take a few minutes. |
@matiasinsaurralde Succesfully merged |
* respect ignored paths in CoProcessMiddleware * add TestGRPCIgnore This is initial test for checking if we have ingore plugin enabled * check ignore on HookType_CustomKeyCheck (cherry picked from commit 8650e18)
/release to release-3-lts |
Working on it! Note that it can take a few minutes. |
* respect ignored paths in CoProcessMiddleware * add TestGRPCIgnore This is initial test for checking if we have ingore plugin enabled * check ignore on HookType_CustomKeyCheck (cherry picked from commit 8650e18)
@matiasinsaurralde Succesfully merged |
/release to release-3.2 |
Working on it! Note that it can take a few minutes. |
@gregdelhon Seems like there is conflict and it require manual merge. |
This adds a check before we process request with coprocess middleware to ensure we skip the middleware when we have
StatusOkAndIgnore
set in context.Related Issue
fixes #3383
Motivation and Context
If you have coprocess set and ignore extended paths. Then the ignored extended paths won't be respected.
How This Has Been Tested
Screenshots (if appropriate)
Types of changes
Checklist
fork, don't request your
master
!master
branch (left side). Also, you should startyour branch off our latest
master
.go mod tidy && go mod vendor
go fmt -s
go vet