config: move require-backend-tls from proxy to security #419
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.
What problem does this PR solve?
Issue Number: close #411
Problem Summary:
require-backend-tls
is more like a security configrequire-backend-tls
is true by default, which causes some compatible problems when updating itWhat is changed and how it works:
require-backend-tls
fromproxy
section tosecurity
require-backend-tls
to falseCheck List
Tests
tiup playground v7.5.0 --tiproxy 1 --tiproxy.binpath /Users/zhangming/gopath/src/github.com/pingcap/tiproxy/bin/tiproxy --tiproxy.config cfg --tiflash 0 cat cfg [proxy] require-backend-tls = false
This proves that it's compatible with the previous config.
Notable changes
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.