-
Notifications
You must be signed in to change notification settings - Fork 202
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
libnetwork: handle id filter better #1497
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@edsantiago PTAL |
By default we should do a standard prefix match. See containers/podman#18471 for context. Also use the c/storage regex package to only compile the regex when needed. Signed-off-by: Paul Holzinger <[email protected]>
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
@@ -38,7 +38,7 @@ func createFilterFuncs(key string, filterValues []string) (types.FilterFunc, err | |||
case "id": | |||
// matches part of one id | |||
return func(net types.Network) bool { | |||
return util.StringMatchRegexSlice(net.ID, filterValues) | |||
return util.FilterID(net.ID, filterValues) |
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.
pkg util
calling another pkg util
is confusing but I see why the function lives in the other util
.
// input is hex we check if the prefix matches. Otherwise we assume it is a | ||
// regex and try to match that. | ||
// see https://github.com/containers/podman/issues/18471 for why we do this | ||
func FilterID(id string, filters []string) bool { |
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.
Code LGTM but all other such functions make it clear that they operate on Slices. Would it make sense to rename FilterID
similarly?
/lgtm |
By default we should do a standard prefix match.
See containers/podman#18471 for context.
Also use the c/storage regex package to only compile the regex when needed.