Improve Config Files (followup from capabilities) #5061
Closed
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.
This is a followup to #4987
It cleans up the config files and renames them into a convention that makes more sense for the current usage. It also fixes
test/local_example.sh
to use etcd2 as the tutorials on vitess.io have switched to it.Full config changes:
One change that it doesn't make, is that the Python default
MYSQL_FLAVOR
is still MariaDB. When I changed this to MySQL56 the testsuite wouldn't pass (it failed in local_example trying to download maven files). This will have to be looked at as a followup.Signed-off-by: Morgan Tocker tocker@gmail.com