v0.29.0

Features

• Make innodb_ft_min_token_size configurable. More about this server parameter can be found here.

v0.28.0

Features

• Upgraded Percona-XtraDB-Cluster to version 5.7.30-31.43
• Internal cluster communication of Galera communication uses more secure algorithm
• Introduced a new property enforce_tls_v1_2 to enforce minimum version TLSv1.2 for client connections to the server

v0.27.0

Features

• Bumped MySQL server to Percona-XtraDB-Cluster-5.7.29-31.43

• Removed the dependency on Python2.7

v0.26.0

Features

• Bumped the Percona xtrabackup version to v2.4.20 which contains CVE fix

v0.25.0

Features

• Added a new BOSH property which sets log formatting to be human-readable

• When deployed as an HA cluster, improved error messaging for some failure scenarios like connection timeout, and when pre-start runs.

v0.24.0

Features

• Make enable_lower_case_table_names, wait_timeout, and default mysql collation_server configurable.

v0.23.0

Features

• New pxc-mysql property called seeded_users can be used to create users via the manifest. Similar to seeded_databases.

  Supported host values are loopback, any, and localhost. loopback corresponds to 127.0.0.1 and any corresponds to %

  Supported role values are minimal and admin. minimal corresponds to usage.

  See spec for examples.

[#171284457]

v0.22.0

Features

• Bumped Percona XtraDB Cluster to v5.7.28-31 [#170064631]

Known Issues

• download-logs reports that fetching MySQL InnoDB Status logs failed, when in reality, it actually succeeded.
  This is a known defect - its because the download-logs tries to download InnoDB Status logs from the jumpbox VM,
  which doesn't exist. It is safe to ignore this error when using the download-logs script.

v0.21.0

Features

• Bumped Percona XtraDB Cluster to v5.7.27
  [#168584227]

• Bumped golang to 1.13
  [#168584227]

• Toggled default for relay_log_recovery. More context is available in the commit.

• download-logs fetches INNODB ENGINE STATUS as well.

Known Issues

• download-logs reports that fetching MySQL InnoDB Status logs failed, when in reality, it actually succeeded. This is a known defect - its because the download-logs tries to download InnoDB Status logs from the jumpbox VM, which don't exist. It is safe to ignore this error when using the download-logs script.

v0.20.0

Features

• Bumped percona-xtrabackup to v2.4.12
  [#165302029]

Bug Fixes

• Stale pid files are cleaned up so that processes start reliably.
  [#167387692]

• Checking the correct Galera property for cluster readiness so that redeploying database works reliably.
  [#167362064]