-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
*: support require-secure-transport startup option (#15341) #15415
*: support require-secure-transport startup option (#15341) #15415
Conversation
Signed-off-by: sre-bot <sre-bot@pingcap.com>
/run-all-tests |
/rebuild |
need merge pingcap/parser#779 first |
1c9aa7f
to
ba7c9bc
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.
LGTM
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
/merge |
1 similar comment
/merge |
/run-all-tests |
@sre-bot merge failed. |
/run-all-tests |
/merge |
/run-all-tests |
cherry pick to release-3.1 in PR #15442 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry-pick #15341 to release-3.0
What problem does this PR solve?
fixes #15306
What is changed and how it works?
--require-secure-transport
startup optionrequire-secure-transport
be enabledrequire-secure-transport
be enabled but no avaliable cert/key/carequire-secure-transport
be enabled event if withno rollback on error
Check List
Tests
Code changes
Side effects
Related changes
tidb-ansible
repositoryRelease note
This change is