dbdeployer 1.10.1

Fix Issue #34 "dbdeployer fails with .mylogin.cnf"

dbdeployer fails when a valid .mylogin.cnf is found in the $HOME directory. The failure is due to the way .mylogin.cnf is designed: it bypasses --no-defaults and --defaults-file (really funny, MySQL team!)

The only known way of using --no-defaults or --defaults-file with .mylogin.cnf is to define an impossible path for it using MYSQL_TEST_LOGIN_FILE environment variable.

dbdeployer does that, and also all the sandbox files use the same workaround.

dbdeployer 1.10.0

• Added command 'dbdeployer admin upgrade sandbox1 sandbox2' (Issue #33)
• Fixed Issue #32 "Error log was not created in data directory"

dbdeployer 1.9.0

ADJUSTMENT

Added option unpack --shell tarball_name

Now dbdeployer can unpack a shell tarball and merge it with the corresponding server.
Also the option --target-server lets us choose where to merge.
See "Installing MySQL shell" in README.md

dbdeployer 1.8.4

Bug fixes and code refactoring

• Fixes Issue#30 "--rpl-user and --db-user should not allow root"

• Remove string literals from options handling
  All flags used on the command line are now defined in the "defaults" package and referred to as variables, rather than using their literal values directly.
  This eliminates some of the risks of handling the wrong option or leaving one option unread.

dbdeployer 1.8.3

Added ./vendor directory

• Better fixes Issue#6 and Issue#27
• Now dependencies are handled directly from the vendor folder.

Fixes Issue#26 "Port management glitch"

• Changed algorithm that finds free ports;
• Uses two separate functions to find single ports and ranges;
• Makes sure that group sandbox creators call the function with the right values (for a "base-port" we check "base-port + 1")
• Added test to check whether sandboxes of adjoining versions deployed in reverse order will end up with the expected port number.

dbdeployer 1.8.0

NEW FEATURES

• Implemented Issue 21 "Add support for directly using path to binaries"

BUGS FIXED

• unpack would not act on old tarball where files were not explicitly marked as regular.
• Fixed Issue 22 "dbdeployer should check whether the binaries are for the current OS"

TESTING

• Added test for Issue 21

dbdeployer 1.7.0

NEW FEATURES

• Added option for custom history file for each sandbox
  (--history-dir=string)
• Added option for unified history file in replication
  sandboxes. (--repl-history-dir boolean)

BUGS FIXED

• Fixed bug in test/functional-test.sh: Some of the subtests were not executed.
• Improved error checking

dbdeployer 1.6.0

NEW FEATURES

Now it is possible to invoke dbdeployer with a short version number, such as 5.7 or 8.0. In this case, dbdeployer will look for the latest release of that MySQL version and use it.

BUGS FIXED

Command line was not saved to dbdeployer catalog

TESTING

• Added test for short versions
• Added test for command line in catalog

dbdeployer 1.5.3

Fixed Issue #16 "Rename during unpack command fails" by making sure the path for sandbox-home and sandbox-binary are absolute ones.

dbdeployer 1.5.2

BUGS FIXED

• Added a stack of cleanup operations for group sandboxes when a depending sandbox installation fails
• Fixed help message of "unpack" command.

ADJUSTMENTS

• When using mysqld-debug, plugins are loaded from $BASEDIR/lib/plugin/debug (https://bugs.mysql.com/bug.php?id=89688)

TESTING

• Added test for data dictionary tables exposure