module-puppetlabs-mysql/examples/mysql_db.pp

class { 'mysql::server':
  root_password => 'password'
}
mysql::db { 'mydb':
  user     => 'myuser',
  password => 'mypass',
  host     => 'localhost',
  grant    => ['SELECT', 'UPDATE'],
}
mysql::db { "mydb_${fqdn}":
  user     => 'myuser',
  password => 'mypass',
  dbname   => 'mydb',
  host     => $::fqdn,
  grant    => ['SELECT', 'UPDATE'],
  tag      => $domain,
}
Allow use different name for db resource other than db name When defining the mysql::db as exported resources, there are chances that the same resource names are defined across the site, which will cause puppet agent fail. By adding an optional dbname parameter, default to the $name, it allows the resouce name to be defined differently, e.g. ${dbname}_${domain}. Also updated test and docs for dbname parameter and add acceptance test for dbname parameter feature 2014-03-07 08:08:09 +01:00			`class { 'mysql::server':`
Fixed test classes Oracle 7 uses mariadb Update PE and OS compatibility info in metadata Now compatible with PE 3.4 and SLES 10. Clean up metadata for new SLES support Add timeout parameter to increase for long time running sql imports Signed-off-by: refnode <refnode@gmail.com> Add documentation for new mysql::db "import_timeout" parameter Signed-off-by: refnode <refnode@gmail.com> Add support for Gentoo The old regex requires something after the 'host' part. Fix this. Old regex is : /^GRANT\s(.+)\sON\s(.+)\sTO\s(.)@(.?)(\s.)$/ . The last part (\s.)$ means "a space followed by anything". The issue is that when user has no GRANT privileges, the "SHOW GRANTS FOR #{user_string}" returns "GRANT SELECT ON `database`.* TO 'user'@'%'" which does not match (\s.)$ . This small patch fixes this making last bloc optional (thanks to '?'). Add explicit dependencies for types mysql_grant has an autorequire()'d dependency on the .my.cnf file used by the provider to talk to the database. I've added this to mysql_database and mysql_user too since logically these also need the file to be in place. I've hit this bug because of a slightly unusual edge case in our own manifests, but I think this fix belongs upstream regardless. (maint) add statement "MANAGED BY PUPPET" to my.cnf config file template and remove unused my.conf.cnf.erb template Improve checks for MySQL user's name. As per http://dev.mysql.com/doc/refman/5.5/en/identifiers.html , MySQL allows for more than '\w-'. This commit improves the check to ensure that: - if username only contains [0-9a-zA-Z$_], it might be quoted. It is not a requirement though - if username contains anything else, it MUST be quoted I kept 2 checks, but the 2nd one can probably be removed (I can't find a username which match the 2nd one but not the first.) Fix escaped backslashes in grants Mysql uses the underscore character to represent a single character wildcard. * A grant on table `the_database`.* would match `theAdatabase`., so underscores must be escaped to avoid this match. The output from mysql escapes special characters (\n, \t, \0, and \\), but the input does not need to be escaped. * In order for the provider to compare the tables, the output of mysql -NBe <query> must have \\ substituted with \. Fixed backup test Oracle 7 uses mariadb Update PE and OS compatibility info in metadata Now compatible with PE 3.4 and SLES 10. Add timeout parameter to increase for long time running sql imports Signed-off-by: refnode <refnode@gmail.com> Add documentation for new mysql::db "import_timeout" parameter Signed-off-by: refnode <refnode@gmail.com> Add support for Gentoo The old regex requires something after the 'host' part. Fix this. Old regex is : /^GRANT\s(.+)\sON\s(.+)\sTO\s(.)@(.?)(\s.)$/ . The last part (\s.)$ means "a space followed by anything". The issue is that when user has no GRANT privileges, the "SHOW GRANTS FOR #{user_string}" returns "GRANT SELECT ON `database`.* TO 'user'@'%'" which does not match (\s.)$ . This small patch fixes this making last bloc optional (thanks to '?'). Add explicit dependencies for types mysql_grant has an autorequire()'d dependency on the .my.cnf file used by the provider to talk to the database. I've added this to mysql_database and mysql_user too since logically these also need the file to be in place. I've hit this bug because of a slightly unusual edge case in our own manifests, but I think this fix belongs upstream regardless. (maint) add statement "MANAGED BY PUPPET" to my.cnf config file template and remove unused my.conf.cnf.erb template Improve checks for MySQL user's name. As per http://dev.mysql.com/doc/refman/5.5/en/identifiers.html , MySQL allows for more than '\w-'. This commit improves the check to ensure that: - if username only contains [0-9a-zA-Z$_], it might be quoted. It is not a requirement though - if username contains anything else, it MUST be quoted I kept 2 checks, but the 2nd one can probably be removed (I can't find a username which match the 2nd one but not the first.) Fix escaped backslashes in grants Mysql uses the underscore character to represent a single character wildcard. * A grant on table `the_database`.* would match `theAdatabase`., so underscores must be escaped to avoid this match. The output from mysql escapes special characters (\n, \t, \0, and \\), but the input does not need to be escaped. * In order for the provider to compare the tables, the output of mysql -NBe <query> must have \\ substituted with \. 2014-10-09 16:47:31 +02:00			`root_password => 'password'`
Allow use different name for db resource other than db name When defining the mysql::db as exported resources, there are chances that the same resource names are defined across the site, which will cause puppet agent fail. By adding an optional dbname parameter, default to the $name, it allows the resouce name to be defined differently, e.g. ${dbname}_${domain}. Also updated test and docs for dbname parameter and add acceptance test for dbname parameter feature 2014-03-07 08:08:09 +01:00			`}`
			`mysql::db { 'mydb':`
			`user => 'myuser',`
			`password => 'mypass',`
			`host => 'localhost',`
			`grant => ['SELECT', 'UPDATE'],`
			`}`
			`mysql::db { "mydb_${fqdn}":`
			`user => 'myuser',`
			`password => 'mypass',`
			`dbname => 'mydb',`
Fix a syntax error in one of the tests. 2014-05-21 20:24:33 +02:00			`host => $::fqdn,`
Allow use different name for db resource other than db name When defining the mysql::db as exported resources, there are chances that the same resource names are defined across the site, which will cause puppet agent fail. By adding an optional dbname parameter, default to the $name, it allows the resouce name to be defined differently, e.g. ${dbname}_${domain}. Also updated test and docs for dbname parameter and add acceptance test for dbname parameter feature 2014-03-07 08:08:09 +01:00			`grant => ['SELECT', 'UPDATE'],`
			`tag => $domain,`
			`}`