feat: Add request-tag extension with version 1.0.0 #1055
Closed
Conversation
This file contains 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
TJKkking
requested review from
Xunzhuo,
2456868764,
CH3CHO,
johnlanni and
WeixinX
as code owners
|
|
TJKkking
force-pushed
the
feature-plugin-traffic-tag
branch
from
f3a71e8
to
3bf6f68
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1055 +/- ##
=======================================
Coverage 35.89% 35.89%
=======================================
Files 69 69
Lines 11549 11549
=======================================
Hits 4146 4146
Misses 7087 7087
Partials 316 316 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ⅰ. Describe what this PR did
This PR introduces a new WASM plugin that enables tagging specific requests based on user-defined rules. The functionality is aimed at facilitating gateway-level gray scaling by tagging requests that meet certain criteria. This can be immensely useful for directing traffic and managing request flows in microservices architectures, especially for testing new features under controlled conditions.
Ⅱ. Does this pull request fix one issue?
No.
Ⅲ. Why don't you add test cases (unit test/integration test)?
Added full e2e test cases.
Ⅳ. Describe how to verify it
https://github.com/alibaba/higress/blob/main/test/README_CN.md#higress-e2e-%E6%B5%8B%E8%AF%95
Ⅴ. Special notes for reviews