Repository navigation
comment out chopusername check - #1009
Merged
Merged
Conversation
Signed-off-by: Suzy Wang <suzy.wang@ibm.com>
Contributor
|
@sunsingerus @Slach this problem prevents us from adopting 0.19.x. I think you'll want to fix this as anybody who specificed an operator password in the config will encounter this. |
Member
|
Also backported to 0.19.3 |
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
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.
Important items to consider before making a Pull Request
Please check items PR complies to:
next-releasebranch, not intomasterbranch1. More infoIn the 1.18.5 version, when clickhouse merges 01-clickhouse-user.xml and chop-generated-users.xml we get
hashed password for plaintext password. When the same is done for the 1.19.0 version, the operator kept both password and hashed password and caused invalid configuration.