Merge pull request #717 from puppetlabs/3.4.x

3.4.0 back to master

Author: bmjen

CHANGELOG.md

@@ -1,3 +1,34 @@
+##2015-05-19 - Supported Release 3.4.0
+###Summary
+This release includes the addition of extra facts, OpenBSD compatibility, and a number of other features, improvements and bug fixes.
+
+####Features/Improvements
+- Added server_id fact which includes mac address for better uniqueness
+- Added OpenBSD compatibility, only for 'OpenBSD -current' (due to the recent switch to mariadb)
+- Added a $mysql_group parameter, and use that instead of the $root_group parameter to define the group membership of the mysql error log file.
+- Updated tests for rspec-puppet 2 and future parser
+- Further acceptance testing improvements
+- MODULES-1928 - allow log-error to be undef
+- Split package installation and database install
+- README wording improvements
+- Added options for including/excluding triggers and routines
+- Made the 'TRIGGER' privilege of mysqldump backups depend on whether or not we are actually backing up triggers
+- Cleaned up the privilege assignment in the mysqldump backup script
+- Add a fact for capturing the mysql version installed
+
+####Bugfixes
+- mysql backup: fix regression in mysql_user call
+- Set service_ensure to undef, in the case of an unmanaged service
+- README Typos fixed
+- Bugfix on Xtrabackup crons
+- Fixed a permission problem that was preventing triggers from being backed up
+- MODULES-1981: Revoke and grant difference of old and new privileges
+- Fix an issue were we assume triggers work
+- Change default for mysql::server::backup to ignore_triggers = false
+
+####Deprecations
+mysql::server::old_root_password property
+
 ##2015-03-03 - Supported Release 3.3.0
 ###Summary
 This release includes major README updates, the addition of backup providers, and a fix for managing the log-bin directory.

README.md

@@ -202,11 +202,11 @@ The MySQL root password. Puppet attempts to set the root password and update `/r
 
 This is required if `create_root_user` or `create_root_my_cnf` are 'true'. If `root_password` is 'UNSET', then `create_root_user` and `create_root_my_cnf` are assumed to be false --- that is, the MySQL root user and `/root/.my.cnf` are not created.
 
-Password changes are supported however the old password must be set in `/root/.my.cnf`. Effectively, Puppet uses the old password, configured in `/root/my.cnf`, to set the new password in MySQL, then updates `/root/.my.cnf` with the new password. 
+Password changes are supported; however, the old password must be set in `/root/.my.cnf`. Effectively, Puppet uses the old password, configured in `/root/my.cnf`, to set the new password in MySQL, and then updates `/root/.my.cnf` with the new password. 
 
 ####`old_root_password`
 
-This parameter no longer does anything. It exists only for backwards compatibility. See the `root_password` parameter for details on changing the root password.
+This parameter no longer does anything. It exists only for backwards compatibility. See the `root_password` parameter above for details on changing the root password.
 
 #####`override_options`
 
@@ -385,7 +385,7 @@ Whether or not to include routines for each database when doing a `file_per_data
 
 #####`include_triggers`
 
-Whether or not to include triggers for a each database when doing a `file_per_database` backup. Defaults to `false`.
+Whether or not to include triggers for each database when doing a `file_per_database` backup. Defaults to `false`.
 
 #####`ensure`
 
@@ -786,13 +786,13 @@ The library file name.
 
 #### `mysql_version`
 
-Determines the MySql version by parsing the output from `mysql --version`
+Determines the MySQL version by parsing the output from `mysql --version`
 
 #### `mysql_server_id`
 
 Generates a unique id, based on the node's MAC address, which can be used as
-`server_id`. This fact will *always* return `0` on all nodes which only have
-loopback interfaces. Given those nodes' connectivity that's probably okay.
+`server_id`. This fact will *always* return `0` on nodes that have only
+loopback interfaces. Because those nodes aren't connected to the outside world, this shouldn't cause any conflicts.
 
 ##Limitations
 

metadata.json

@@ -1,6 +1,6 @@
 {
   "name": "puppetlabs-mysql",
-  "version": "3.3.0",
+  "version": "3.4.0",
   "author": "Puppet Labs",
   "summary": "Installs, configures, and manages the MySQL service.",
   "license": "Apache-2.0",