Conversation
|
|
Author
|
Hey @rektdeckard! saw you reviewed the other token changes, would you mind taking a look at this when you get a chance? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
selecting Ingress in
lk token createwasn't settingingressAdmin, even though--ingressdid.this sets the grant from the wizard selection. added a regression for ingress, egress and combined permissions. the pty dependency is already present transitively and is only used by the test.
i manually tested it e2e with the compiled CLI and a local LiveKit server. the wizard token was rejected by
ListIngressbefore the fix and accepted afterward.--ingressworked both times. also checked the other options and combined permissions.