-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Allow --no-rbac flag that allows users to not pass rbac config #9972
Merged
Conversation
This file contains 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
Signed-off-by: notfelineit <notfelineit@gmail.com>
ajm188
reviewed
Mar 24, 2022
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.
all i've got are style commentary!
Signed-off-by: notfelineit <notfelineit@gmail.com>
ajm188
reviewed
Mar 24, 2022
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.
one more round 😅
Co-authored-by: Andrew Mason <andrew@planetscale.com>
notfelineit
commented
Mar 24, 2022
notfelineit
commented
Mar 24, 2022
Signed-off-by: notfelineit <notfelineit@gmail.com>
fccbb90
to
4c03621
Compare
ajm188
approved these changes
Mar 24, 2022
Signed-off-by: notfelineit <notfelineit@gmail.com>
ajm188
pushed a commit
to planetscale/vitess
that referenced
this pull request
Apr 5, 2022
This was introduced and made a required flag (with mutually-exclusive `--no-rbac`) in vitessio#9972. Signed-off-by: Andrew Mason <andrew@planetscale.com>
ajm188
pushed a commit
that referenced
this pull request
Apr 5, 2022
* Add `--rbac` to example vtadmin-up This was introduced and made a required flag (with mutually-exclusive `--no-rbac`) in #9972. Signed-off-by: Andrew Mason <andrew@planetscale.com> * Cleanup `Options.Services`, and inspect the ServiceInfo() directly Instead of requiring users to know in advance (and put into their startup scripts), which services will run, we can (correctly) inspect the service names that have been registered on the underlying grpc.Server and mark them as SERVING in the health service. _Alsooooo_, this was never bound to a flag, so users couldn't use it anyway! Whoops. Signed-off-by: Andrew Mason <andrew@planetscale.com> * Provide option to enable channelz service Signed-off-by: Andrew Mason <andrew@planetscale.com> * Add flag to enable channelz Signed-off-by: Andrew Mason <andrew@planetscale.com> * Tidy up flags; label all sections Signed-off-by: Andrew Mason <andrew@planetscale.com> * Add missing flag for AllowTracing Signed-off-by: Andrew Mason <andrew@planetscale.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: notfelineit notfelineit@gmail.com
Description
Breaking Change
This PR adds a flag
--no-rbac
that allows users to bypass passing the flag--rbac-config
. In doing so, a default rbac configuration is used:It also makes it so that a user must explicitly pass in either
![Screen Shot 2022-03-23 at 4 59 44 PM](https://user-images.githubusercontent.com/31225471/159816169-33deb8e3-73f4-465a-a0bb-30e9e7ef5c1e.png)
--no-rbac
or--rbac
, otherwise vtadmin will fail to come up:This is a breaking change since users who were using
--rbac-config
must now explicitly pass in--rbac
flag as well.Cases
--no-rbac
:--rbac
:Failing to pass in either flag:
![Screen Shot 2022-03-23 at 4 59 44 PM](https://user-images.githubusercontent.com/31225471/159816244-8c096814-e687-4056-85dd-e3dd601c7804.png)
Related Issue(s)
This addresses this issue: #9419
Checklist
Deployment Notes
N/A