-
Notifications
You must be signed in to change notification settings - Fork 96
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
multi: support using a regex when specifying custom perms #450
Conversation
ce2c146
to
ebde9ea
Compare
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.
This looks good, just found one typo.
Going to use this branch while testing my permission changes 👍
@ellemouton, remember to re-request review from reviewers when ready |
ebde9ea
to
06138ea
Compare
06138ea
to
2819fc6
Compare
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.
Nice work! Pretty straightforward implementation, just an idea for making it even more generic.
2819fc6
to
77fbaaf
Compare
77fbaaf
to
22b891b
Compare
@itsrachelfish , this is ready for a final review :) |
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.
tACK, regex support works, but the examples & tests could be updated to be more clear.
With this commit, a user can now specify a regex when specifying custom permissions for an LNC session. This regex will be used to select permissions for URIs that match the regex.
22b891b
to
15cd1bd
Compare
With this PR, you can now use the wild card character when specifying custom URIs that permissions should be added for in an LNC session. This allows you to do the following:
The above will create a session that has the perms to only access the
ListChannels
call of thelnrpc.Lightning
but then also has the perms to access any URI that falls under thepoolrpc.Trader
service.`
Fixes #439