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.
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
api: refactor ACL check for namespace wildcard #13606
api: refactor ACL check for namespace wildcard #13606
Changes from 2 commits
0a050f7
0b9ca17
a7a06b8
de40f4d
00ec288
b092818
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
It feels like passing an empty op is a programmer error, not a condition we intentionally support. Should this return
ErrPermissionDenied
so that we can catch that in testing?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.
Yeah, I didn't like this very much but figured it was OK given it's a private method. The key is that it needs to differentiate between two scenarios:
AllowNamespaceOperation
needs to know if any namespace allows a specific operationAllowNamespace
needs to know if any namespace allows any operation (i.e., all don't deny)Having a "magic" input (empty string in this case) serves as that switch between the two cases.
But looking at the code I found a better way to do it, so thanks for raising it!
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.
New approach in commit a7a06b8
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.
do we not need to check this is okay? if we can statically assert, shouldn't the checkFn parameter be a
capabilitySet
?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.
checkFn
needs to be aWalkFn
, so the signature is pretty set.This iterates over the internal tree of namespaces, if there's data that is not a
capabilitySet
then something pretty wrong happened 😅findAllMatchingWildcards
doesn't have the check either, so I think it's safe to assume this would always work?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.
Ahh I see, yup just ignore me!