-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add docs for dynamic privileges #6407
Conversation
/lgtm |
@bb7133: Please use GitHub review feature instead of For the reason we drop support to the commands, see also this page. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
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.
Please also update Line 487.
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
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
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/remove-status LGT1 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: a4a6108
|
/merge |
First-time contributors' checklist
What is changed, added or deleted? (Required)
This feature documents pingcap/tidb#22778 which has not yet merged. It only applies to master, and fixes a couple of other small bugs (around
password
->authentication_string
).The list of "Privileges required for TiDB operations" is changed to an example, because the list does not account for dynamic privileges so it gets confusing.
The PR includes comments for where the version after 5.0 will need to be inserted. Thus, the PR should be labeled as requiring followup after merging as well.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?