http: return per route config when direct response is set#17449
http: return per route config when direct response is set#17449mattklein123 merged 14 commits intoenvoyproxy:mainfrom
Conversation
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
|
/retest |
|
Retrying Azure Pipelines: |
mattklein123
left a comment
There was a problem hiding this comment.
Thanks for fixing! One question.
/wait-any
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
|
/retest |
|
Retrying Azure Pipelines: |
mattklein123
left a comment
There was a problem hiding this comment.
Thanks, looks great. One small comment.
/wait
| void RouteEntryImplBase::traversePerFilterConfig( | ||
| const std::string& filter_name, | ||
| std::function<void(const Router::RouteSpecificFilterConfig&)> cb) const { | ||
| const Router::RouteEntry* route_entry = routeEntry(); |
There was a problem hiding this comment.
Isn't this the same bug? Shouldn't we not be gating this on routeEntry()? Or are you not fixing this because you want it changes extauth and you want to fix this separately? If the latter can you add a comment/TODO here?
There was a problem hiding this comment.
Yes, I plan to fix this in separate PR, along with #17502, Let me add a todo.
Actually, I'm a little confused about the separate PR. I used to use gerrit before. Everybody is reviewing the each commit and merge each commit separately. But PR includes multiple commits, but look like people doesn't care about how many commits in a PR. But let me know what is preference way people do here :)
There was a problem hiding this comment.
We squash all the commits when we merge, so just add as many commits as you want. The GH review system is very bad compared to Gerrit and this is the only way to make it reasonably work.
|
/retest |
|
Retrying Azure Pipelines: |
|
Sorry looks like this needs a main merge. /wait |
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
done |
|
Sorry can you merge main again which should fix the verify examples breakage? /wait |
Signed-off-by: He Jie Xu <hejie.xu@intel.com>
haha, did merge again :) |
|
/retest |
|
Retrying Azure Pipelines: |
|
/backport This results in broken configs, with no workaround. |
…bridge-stream * upstream/main: (32 commits) tls: move ssl connection info into SocketAddressProvider (envoyproxy#17334) conn pool: default enable runtime feature `conn_pool_delete_when_idle` (envoyproxy#17577) api: LEDS api introduction (envoyproxy#17419) kafka: add support for api versions request in mesh-filter (envoyproxy#17475) ext_proc: Implement BUFFERED_PARTIAL processing mode (envoyproxy#17531) tooling: Async/pathlib/mypy cleanups and utils (envoyproxy#17505) xds: restructure CertificateProvider fields (envoyproxy#17201) Refactor OverloadIntegrationTest breaking out a test base, and the fake resource monitors. (envoyproxy#17530) listener: move active connection collection out of active tcp listener (envoyproxy#16947) tools: format checks for backticks (envoyproxy#17566) coverage: set lower limit for common/quic and common (envoyproxy#17573) v2: final source removal (envoyproxy#17565) test: bumping coverage (envoyproxy#17564) quic: enforcing header size and contents (envoyproxy#17520) Support for canonicalizing URI properly for AWS SigV4 signer (envoyproxy#17137) listener: add a stat for transport socket connect timeout (envoyproxy#17458) listener: add listen() error handling (envoyproxy#17427) http: return per route config when direct response is set (envoyproxy#17449) removing most v2 references from source/ (envoyproxy#17415) bug fix: return bootstrap when validating config (envoyproxy#17499) ... Signed-off-by: Garrett Bourg <bourg@squareup.com>
Backport of envoyproxy#17449, e071417 Co-authored-by: He Jie Xu <hejie.xu@intel.com> Signed-off-by: Greg Greenway <ggreenway@apple.com>
…#17449) Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Commit Message: http: return per route config when direct response is set
Additional Description:
When the direct response is set, the
Route::routeEntry()could benullptr, but itdoesn't mean there is no per route typed config. So the most specific route config
should be able to get from the
class Route. So move themostSpecificPerFilterConfigTypedinterface into class
Route.Risk Level: low
Testing: unittest
Docs Changes: n/a
Release Notes: n/a
[Optional Runtime guard:]
Fixes #17377
Signed-off-by: He Jie Xu hejie.xu@intel.com