Repository navigation
[ISSUE #14695] Support tagv2 gray rules - #15255
Conversation
537cc73 to
67496b5
Compare
67496b5 to
eb2d845
Compare
|
@KiteSoar CLA is green and this PR is ready for review. Could you take a look when convenient? |
|
@KomachiSion CLA is green and this PR is ready for review. Could you take a look when convenient? |
|
reopen for ci |
|
Thanks for your this PR. 🙏 感谢您提交的PR。 🙏 |
eb2d845 to
0663ec8
Compare
Change-Id: I61ec478a5e7bc825858ad520159a706f8db4921f
0663ec8 to
20c88a5
Compare
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
What is the purpose of the change
Closes #14695.
This PR syncs the existing internal Nacos tagv2 gray rule implementation into the open-source config module, so the open-source and internal branches keep the same gray rule model and behavior.
This change keeps the query path compatible with the current open-source request model. It does not add HTTP request label query support in this PR; SDK/gRPC labels continue to flow through the existing connection labels path.
Brief changelog
GrayRuleimplementations with SPI registration.ConfigOperationService.publishConfigGrayfrom the v3 admin controller.Verifying this change
./mvnw -pl config -am -Dtest=SingleTagMatchGrayRuleTest,MultiTagMatchGrayRuleTest,GrayRuleManagerTest,ConfigControllerV3Test -Dsurefire.failIfNoSpecifiedTests=false test