-
Notifications
You must be signed in to change notification settings - Fork 2.6k
feat(consul): filter nodes in upstream with metadata #12448
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
Open
jizhuozhi
wants to merge
10
commits into
apache:master
Choose a base branch
from
jizhuozhi:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+239
−14
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
0e23e48
feat(consul): filter nodes in upstream with metadata
jizhuozhi c188c50
feat(consul): filter nodes in upstream with metadata
jizhuozhi cae7c04
feat(consul): filter nodes in upstream with metadata
jizhuozhi 1fec8e3
feat(consul): filter nodes in upstream with metadata
jizhuozhi 3867b84
feat(consul): filter nodes in upstream with metadata
jizhuozhi 2e7a2df
feat(consul): filter nodes in upstream with metadata
jizhuozhi 9cd9451
feat(consul): filter nodes in upstream with metadata
dfd4ad2
feat(consul): filter nodes in upstream with metadata
jizhuozhi 225cb4a
feat(consul): filter nodes in upstream with metadata
jizhuozhi d0243d9
feat(consul): filter nodes in upstream with metadata
jizhuozhi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
-- | ||
-- Licensed to the Apache Software Foundation (ASF) under one or more | ||
-- contributor license agreements. See the NOTICE file distributed with | ||
-- this work for additional information regarding copyright ownership. | ||
-- The ASF licenses this file to You under the Apache License, Version 2.0 | ||
-- (the "License"); you may not use this file except in compliance with | ||
-- the License. You may obtain a copy of the License at | ||
-- | ||
-- http://www.apache.org/licenses/LICENSE-2.0 | ||
-- | ||
-- Unless required by applicable law or agreed to in writing, software | ||
-- distributed under the License is distributed on an "AS IS" BASIS, | ||
-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
-- See the License for the specific language governing permissions and | ||
-- limitations under the License. | ||
-- | ||
local core = require("apisix.core") | ||
local ipairs = ipairs | ||
local pairs = pairs | ||
|
||
local _M = {} | ||
|
||
local function do_metadata_match(node, metadata_match) | ||
local metadata = node.metadata | ||
-- because metadata_match has already been checked in nodes_metadata_match, | ||
-- there is at least one role, if there is no metadata in node, it's must not matched | ||
if not metadata then | ||
return false | ||
end | ||
for key, values in pairs(metadata_match) do | ||
local matched = false | ||
for _, value in ipairs(values) do | ||
if metadata[key] == value then | ||
matched = true | ||
break | ||
end | ||
end | ||
if not matched then | ||
return false | ||
end | ||
end | ||
return true | ||
end | ||
|
||
local function nodes_metadata_match(nodes, metadata_match) | ||
if not nodes then | ||
return nil | ||
end | ||
|
||
-- fast path: there is not metadata_match roles, all nodes are available, | ||
-- and make a guarantee for do_metadata_match: at least one role | ||
if not metadata_match then | ||
return nodes | ||
end | ||
|
||
local result = {} | ||
for _, node in ipairs(nodes) do | ||
if do_metadata_match(node, metadata_match) then | ||
core.table.insert(result, node) | ||
end | ||
end | ||
return result | ||
end | ||
_M.nodes_metadata_match = nodes_metadata_match | ||
|
||
return _M |
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
@jizhuozhi I've found a problem. If I understand correctly, the current test only checks routing to
v2
andv3
, but it's missing the cases after adding or removingmetadata_match
. For example, adding- v4
and removing- v2
means the request should only be routed to those marked asv3
orv4
.Maybe I missed something, please trouble you to answer or add the cases.
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.
Yes, after adding
- v4
and removing- v2
, the request should only be routed to those marked asv3
orv4
.It seems to be equivalent to the current test case, as
discovery_args
is atomic updated, however I will add new case with adding- v4
and removing- v2
means the request should only be routed to those marked asv3
orv4
:)Uh oh!
There was an error while loading. Please reload this page.
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.
@jizhuozhi The intention is to prove that after the configuration is updated, the data can correctly point to their marks.
Perhaps there's a better way to describe this situation, what are your thoughts?
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.
@jizhuozhi Hello, may I ask if there's any progress?