Bugfix for WSREP SST auth config typo #68
Merged
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.
Description
When I implemented the WSREP SST auth configuration I made a typo for the default value of wsrep_sst_auth. It is currently set to the variable used to configure MySQL user instead of pair [username]:[password]. The default value for wsrep_sst_auth should be set to:
This issue passed through tests because they do not cover the scenario of using mariabackup SST nor TLS encrypted SST. I do not intend to implement it now, maybe someday when more people will use these features.
Related Issue
Types of changes
Checklist: