Version information
This version is compatible with:
- Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 3.0.0 < 5.0.0
- , , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'adam8723-mysql', '3.11.1'
Learn more about managing modules with a PuppetfileDocumentation
mysql
Table of Contents
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with mysql
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Module Description
The mysql module installs, configures, and manages the MySQL service.
This module manages both the installation and configuration of MySQL, as well as extending Puppet to allow management of MySQL resources, such as databases, users, and grants.
Setup
Beginning with mysql
To install a server with the default options:
include '::mysql::server'
.
To customize options, such as the root password or /etc/my.cnf
settings, you must also pass in an override hash:
class { '::mysql::server':
root_password => 'strongpassword',
remove_default_accounts => true,
override_options => $override_options
}
See Customize Server Options below for examples of the hash structure for $override_options.
Usage
All interaction for the server is done via mysql::server
. To install the client, use mysql::client
. To install bindings, use mysql::bindings
.
Customize server options
To define server options, structure a hash structure of overrides in mysql::server
. This hash resembles a hash in the my.cnf file:
$override_options = {
'section' => {
'item' => 'thing',
}
}
For options that you would traditionally represent in this format:
[section]
thing = X
Entries can be created as thing => true
, thing => value
, or thing => ""
in the hash. Alternatively, you can pass an array as thing => ['value', 'value2']
or list each thing => value
separately on individual lines.
You can pass a variable in the hash without setting a value for it; the variable would then use MySQL's default settings. To exclude an option from the my.cnf
file --- for example, when using override_options
to revert to a default value --- pass thing => undef
.
If an option needs multiple instances, pass an array. For example,
$override_options = {
'mysqld' => {
'replicate-do-db' => ['base1', 'base2'],
}
}
produces
[mysqld]
replicate-do-db = base1
replicate-do-db = base2
To implement version specific parameters, specify the version, such as [mysqld-5.5]. This allows one config for different versions of MySQL.
Create a database
To create a database with a user and some assigned privileges:
mysql::db { 'mydb':
user => 'myuser',
password => 'mypass',
host => 'localhost',
grant => ['SELECT', 'UPDATE'],
}
To use a different resource name with exported resources:
@@mysql::db { "mydb_${fqdn}":
user => 'myuser',
password => 'mypass',
dbname => 'mydb',
host => ${fqdn},
grant => ['SELECT', 'UPDATE'],
tag => $domain,
}
Then you can collect it on the remote DB server:
Mysql::Db <<| tag == $domain |>>
If you set the sql parameter to a file when creating a database, the file is imported into the new database.
For large sql files, increase the import_timeout
parameter, which defaults to 300 seconds.
mysql::db { 'mydb':
user => 'myuser',
password => 'mypass',
host => 'localhost',
grant => ['SELECT', 'UPDATE'],
sql => '/path/to/sqlfile.gz',
import_cat_cmd => 'zcat',
import_timeout => 900,
}
Customize configuration
To add custom MySQL configuration, place additional files into includedir
. This allows you to override settings or add additional ones, which is helpful if you don't use override_options
in mysql::server
. The includedir
location is by default set to /etc/mysql/conf.d
.
Work with an existing server
To instantiate databases and users on an existing MySQL server, you need a .my.cnf
file in root
's home directory. This file must specify the remote server address and credentials. For example:
[client]
user=root
host=localhost
password=secret
This module uses the mysqld_version
fact to discover the server version being used. By default, this is set to the output of mysqld -V
. If you're working with a remote MySQL server, you may need to set a custom fact for mysqld_version
to ensure correct behaviour.
When working with a remote server, do not use the mysql::server
class in your Puppet manifests.
Specify passwords
In addition to passing passwords as plain text, you can input them as hashes. For example:
mysql::db { 'mydb':
user => 'myuser',
password => '*6C8989366EAF75BB670AD8EA7A7FC1176A95CEF4',
host => 'localhost',
grant => ['SELECT', 'UPDATE'],
}
Install Percona server on CentOS
This example shows how to do a minimal installation of a Percona server on a CentOS system. This sets up the Percona server, client, and bindings (including Perl and Python bindings). You can customize this usage and update the version as needed.
This usage has been tested on Puppet 4.4 / CentOS 7 / Percona Server 5.7.
Note: The installation of the yum repository is not part of this package and is here only to show a full example of how you can install.
yumrepo { 'percona':
descr => 'CentOS $releasever - Percona',
baseurl => 'http://repo.percona.com/centos/$releasever/os/$basearch/',
gpgkey => 'http://www.percona.com/downloads/percona-release/RPM-GPG-KEY-percona',
enabled => 1,
gpgcheck => 1,
}
class {'mysql::server':
package_name => 'Percona-Server-server-57',
package_ensure => '5.7.11-4.1.el7',
service_name => 'mysql',
config_file => '/etc/my.cnf',
includedir => '/etc/my.cnf.d',
root_password => 'PutYourOwnPwdHere',
override_options => {
mysqld => {
log-error => '/var/log/mysqld.log',
pid-file => '/var/run/mysqld/mysqld.pid',
},
mysqld_safe => {
log-error => '/var/log/mysqld.log',
},
}
}
# Note: Installing Percona-Server-server-57 also installs Percona-Server-client-57.
# This shows how to install the Percona MySQL client on its own
class {'mysql::client':
package_name => 'Percona-Server-client-57',
package_ensure => '5.7.11-4.1.el7',
}
# These packages are normally installed along with Percona-Server-server-57
# If you needed to install the bindings, however, you could do so with this code
class { 'mysql::bindings':
client_dev_package_name => 'Percona-Server-shared-57',
client_dev_package_ensure => '5.7.11-4.1.el7',
client_dev => true,
daemon_dev_package_name => 'Percona-Server-devel-57',
daemon_dev_package_ensure => '5.7.11-4.1.el7',
daemon_dev => true,
perl_enable => true,
perl_package_name => 'perl-DBD-MySQL',
python_enable => true,
python_package_name => 'MySQL-python',
}
# Dependencies definition
Yumrepo['percona']->
Class['mysql::server']
Yumrepo['percona']->
Class['mysql::client']
Yumrepo['percona']->
Class['mysql::bindings']
Install MariaDB on Ubuntu
Optional: Install the MariaDB official repo
In this example, we'll use the latest stable (currently 10.1) from the official MariaDB repository, not the one from the distro repository. You could instead use the package from the Ubuntu repository. Make sure you use the repository corresponding to the version you want.
Note: sfo1.mirrors.digitalocean.com
is one of many mirrors available. You can use any official mirror.
include apt
apt::source { 'mariadb':
location => 'http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu',
release => $::lsbdistcodename,
repos => 'main',
key => {
id => '199369E5404BD5FC7D2FE43BCBCB082A1BB943DB',
server => 'hkp://keyserver.ubuntu.com:80',
},
include => {
src => false,
deb => true,
},
}
Install the MariaDB server
This example shows MariaDB server installation on Ubuntu Trusty. Adjust the version and the parameters of my.cnf
as needed. All parameters of the my.cnf
can be defined using the override_options
parameter.
The folders /var/log/mysql
and /var/run/mysqld
are created automatically, but if you are using other custom folders, they should exist as prerequisites for this code.
All the values set here are an example of a working minimal configuration.
Specify the version of the package you want with the package_ensure
parameter.
class {'::mysql::server':
package_name => 'mariadb-server',
package_ensure => '10.1.14+maria-1~trusty',
service_name => 'mysql',
root_password => 'AVeryStrongPasswordUShouldEncrypt!',
override_options => {
mysqld => {
'log-error' => '/var/log/mysql/mariadb.log',
'pid-file' => '/var/run/mysqld/mysqld.pid',
},
mysqld_safe => {
'log-error' => '/var/log/mysql/mariadb.log',
},
}
}
# Dependency management. Only use that part if you are installing the repository
# as shown in the Preliminary step of this example.
Apt::Source['mariadb'] ~>
Class['apt::update'] ->
Class['::mysql::server']
Install the MariaDB client
This example shows how to install the MariaDB client and all of the bindings at once. You can do this installation separately from the server installation.
Specify the version of the package you want with the package_ensure
parameter.
class {'::mysql::client':
package_name => 'mariadb-client',
package_ensure => '10.1.14+maria-1~trusty',
bindings_enable => true,
}
# Dependency management. Only use that part if you are installing the repository as shown in the Preliminary step of this example.
Apt::Source['mariadb'] ~>
Class['apt::update'] ->
Class['::mysql::client']
Reference
Classes
Public classes
mysql::server
: Installs and configures MySQL.mysql::server::monitor
: Sets up a monitoring user.mysql::server::mysqltuner
: Installs MySQL tuner script.mysql::server::backup
: Sets up MySQL backups via cron.mysql::bindings
: Installs various MySQL language bindings.mysql::client
: Installs MySQL client (for non-servers).
Private classes
mysql::server::install
: Installs packages.mysql::server::installdb
: Implements setup of mysqld data directory (e.g. /var/lib/mysql)mysql::server::config
: Configures MYSQL.mysql::server::service
: Manages service.mysql::server::account_security
: Deletes default MySQL accounts.mysql::server::root_password
: Sets MySQL root password.mysql::server::providers
: Creates users, grants, and databases.mysql::bindings::client_dev
: Installs MySQL client development package.mysql::bindings::daemon_dev
: Installs MySQL daemon development package.mysql::bindings::java
: Installs Java bindings.mysql::bindings::perl
: Installs Perl bindings.mysql::bindings::php
: Installs PHP bindings.mysql::bindings::python
: Installs Python bindings.mysql::bindings::ruby
: Installs Ruby bindings.mysql::client::install
: Installs MySQL client.mysql::backup::mysqldump
: Implements mysqldump backups.mysql::backup::mysqlbackup
: Implements backups with Oracle MySQL Enterprise Backup.mysql::backup::xtrabackup
: Implements backups with XtraBackup from Percona.
Parameters
mysql::server
create_root_user
Whether root user should be created.
Valid values are true
, false
.
Defaults to true
.
This is useful for a cluster setup with Galera. The root user has to be created only once. You can set this parameter true on one node and set it to false on the remaining nodes.
create_root_my_cnf
Whether to create /root/.my.cnf
.
Valid values are true
, false
.
Defaults to true
.
create_root_my_cnf
allows creation of /root/.my.cnf
independently of create_root_user
. You can use this for a cluster setup with Galera where you want /root/.my.cnf
to exist on all nodes.
root_password
The MySQL root password. Puppet attempts to set the root password and update /root/.my.cnf
with it.
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, 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 above for details on changing the root password.
override_options
Specifies override options to pass into MySQL. Structured like a hash in the my.cnf file:
$override_options = {
'section' => {
'item' => 'thing',
}
}
See Customize Server Options above for usage details.
config_file
The location, as a path, of the MySQL configuration file.
manage_config_file
Whether the MySQL configuration file should be managed.
Valid values are true
, false
.
Defaults to true
.
includedir
The location, as a path, of !includedir for custom configuration overrides.
install_options
Passes install_options array to managed package resources. You must pass the appropriate options for the specified package manager.
purge_conf_dir
Whether the includedir
directory should be purged.
Valid values are true
, false
.
Defaults to false
.
restart
Whether the service should be restarted when things change.
Valid values are true
, false
.
Defaults to false
.
root_group
The name of the group used for root. Can be a group name or a group ID. See more about the group
file attribute.
mysql_group
The name of the group of the MySQL daemon user. Can be a group name or a group ID. See more about the group
file attribute.
package_ensure
Whether the package exists or should be a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
Defaults to 'present'.
package_manage
Whether to manage the MySQL server package.
Defaults to true
.
package_name
The name of the MySQL server package to install.
remove_default_accounts
Specifies whether to automatically include mysql::server::account_security
.
Valid values are true
, false
.
Defaults to false
.
service_enabled
Specifies whether the service should be enabled.
Valid values are true
, false
.
Defaults to true
.
service_manage
Specifies whether the service should be managed.
Valid values are true
, false
.
Defaults to true
.
service_name
The name of the MySQL server service.
Defaults are OS dependent, defined in 'params.pp'.
service_provider
The provider to use to manage the service.
For Ubuntu, defaults to 'upstart'; otherwise, default is undefined.
users
Optional hash of users to create, which are passed to mysql_user.
users => {
'someuser@localhost' => {
ensure => 'present',
max_connections_per_hour => '0',
max_queries_per_hour => '0',
max_updates_per_hour => '0',
max_user_connections => '0',
password_hash => '*F3A2A51A9B0F2BE2468926B4132313728C250DBF',
tls_options => ['NONE'],
},
}
grants
Optional hash of grants, which are passed to mysql_grant.
grants => {
'someuser@localhost/somedb.*' => {
ensure => 'present',
options => ['GRANT'],
privileges => ['SELECT', 'INSERT', 'UPDATE', 'DELETE'],
table => 'somedb.*',
user => 'someuser@localhost',
},
}
databases
Optional hash of databases to create, which are passed to mysql_database.
databases => {
'somedb' => {
ensure => 'present',
charset => 'utf8',
},
}
mysql::server::backup
backupuser
MySQL user to create for backups.
backuppassword
MySQL user password for backups.
backupdir
Directory in which to store backups.
backupdirmode
Permissions applied to the backup directory. This parameter is passed directly to the file
resource.
backupdirowner
Owner for the backup directory. This parameter is passed directly to the file
resource.
backupdirgroup
Group owner for the backup directory. This parameter is passed directly to the file
resource.
backupcompress
Whether backups should be compressed.
Valid values are true
, false
.
Defaults to true
.
backuprotate
How many days to keep backups.
Valid value is an integer.
Defaults to 30.
delete_before_dump
Whether to delete old .sql files before backing up. Setting to true deletes old files before backing up, while setting to false deletes them after backup.
Valid values are true
, false
.
Defaults to false
.
backupdatabases
Specifies an array of databases to back up.
file_per_database
Whether a separate file be used per database.
Valid values are true
, false
.
Defaults to false
.
include_routines
Whether or not to include routines for each database when doing a file_per_database
backup.
Defaults to false
.
include_triggers
Whether or not to include triggers for each database when doing a file_per_database
backup.
Defaults to false
.
ensure
Allows you to remove the backup scripts.
Valid values are 'present', 'absent'.
Defaults to 'present'.
execpath
Allows you to set a custom PATH should your MySQL installation be non-standard places. Defaults to /usr/bin:/usr/sbin:/bin:/sbin
.
time
An array of two elements to set the backup time. Allows ['23', '5'] (i.e., 23:05) or ['3', '45'] (i.e., 03:45) for HH:MM times.
mysql::server::backup
postscript
A script that is executed when the backup is finished. This could be used to sync the backup to a central store. This script can be either a single line that is directly executed or a number of lines supplied as an array. It could also be one or more externally managed (executable) files.
prescript
A script that is executed before the backup begins.
provider
Sets the server backup implementation. Valid values are:
mysqldump
: Implements backups with mysqldump. Backup type: Logical. This is the default value.mysqlbackup
: Implements backups with MySQL Enterprise Backup from Oracle. Backup type: Physical. To use this type of backup, you'll need themeb
package, which is available in RPM and TAR formats from Oracle. For Ubuntu, you can use meb-deb to create a package from an official tarball.xtrabackup
: Implements backups with XtraBackup from Percona. Backup type: Physical.
maxallowedpacket
Defines the maximum SQL statement size for the backup dump script. The default value is 1MB, as this is the default MySQL Server value.
optional_args
Specifies an array of optional arguments which should be passed through to the backup tool. (Currently only supported by the xtrabackup provider.)
mysql::server::monitor
mysql_monitor_username
The username to create for MySQL monitoring.
mysql_monitor_password
The password to create for MySQL monitoring.
mysql_monitor_hostname
The hostname from which the monitoring user requests are allowed access.
mysql::server::mysqltuner
Note: If you're using this class on a non-network-connected system, you must download the mysqltuner.pl script and have it hosted somewhere accessible via http(s)://
, puppet://
, ftp://
, or a fully qualified file path.
ensure
Ensures that the resource exists.
Valid values are 'present', 'absent'.
Defaults to 'present'.
version
The version to install from the major/MySQLTuner-perl github repository. Must be a valid tag.
Defaults to 'v1.3.0'.
environment
Environment variables acive during download, e.g. to download via proxies: environment => 'https_proxy=http://proxy.example.com:80'
mysql::bindings
client_dev
Specifies whether ::mysql::bindings::client_dev
should be included.
Valid values are true
', false
.
Defaults to false
.
daemon_dev
Specifies whether ::mysql::bindings::daemon_dev
should be included.
Valid values are true
, false
.
Defaults to false
.
java_enable
Specifies whether ::mysql::bindings::java
should be included.
Valid values are true
, false
.
Defaults to false
.
perl_enable
Specifies whether mysql::bindings::perl
should be included.
Valid values are true
, false
.
Defaults to false
.
php_enable
Specifies whether mysql::bindings::php
should be included.
Valid values are true
, false
.
Defaults to false
.
python_enable
Specifies whether mysql::bindings::python
should be included.
Valid values are true
, false
.
Defaults to false
.
ruby_enable
Specifies whether mysql::bindings::ruby
should be included.
Valid values are true
, false
.
Defaults to false
.
install_options
Passes install_options
array to managed package resources. You must pass the appropriate options for the package manager(s).
client_dev_package_ensure
Whether the package should be present, absent, or a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
Only applies if client_dev => true
.
client_dev_package_name
The name of the client_dev package to install.
Only applies if client_dev => true
.
client_dev_package_provider
The provider to use to install the client_dev package.
Only applies if client_dev => true
.
daemon_dev_package_ensure
Whether the package should be present, absent, or a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
Only applies if daemon_dev => true
.
daemon_dev_package_name
The name of the daemon_dev package to install.
Only applies if daemon_dev => true
.
daemon_dev_package_provider
The provider to use to install the daemon_dev package.
Only applies if daemon_dev => true
.
java_package_ensure
Whether the package should be present, absent, or a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
Only applies if java_enable => true
.
java_package_name
The name of the Java package to install.
Only applies if java_enable => true
.
java_package_provider
The provider to use to install the Java package.
Only applies if java_enable => true
.
perl_package_ensure
Whether the package should be present, absent, or a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
Only applies if perl_enable => true
.
perl_package_name
The name of the Perl package to install.
Only applies if perl_enable => true
.
perl_package_provider
The provider to use to install the Perl package.
Only applies if perl_enable => true
.
php_package_ensure
Whether the package should be present, absent, or a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
Only applies if php_enable => true
.
php_package_name
The name of the PHP package to install.
Only applies if php_enable => true
.
python_package_ensure
Whether the package should be present, absent, or a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
Only applies if python_enable => true
.
python_package_name
The name of the Python package to install.
Only applies if python_enable => true
.
python_package_provider
The provider to use to install the Python package.
Only applies if python_enable => true
.
ruby_package_ensure
Whether the package should be present, absent, or a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
Only applies if ruby_enable => true
.
ruby_package_name
The name of the Ruby package to install.
Only applies if ruby_enable => true
.
ruby_package_provider
What provider should be used to install the package.
mysql::client
bindings_enable
Whether to automatically install all bindings.
Valid values are true
, false
.
Default to false
.
install_options
Array of install options for managed package resources. You must pass the appropriate options for the package manager.
package_ensure
Whether the MySQL package should be present, absent, or a specific version.
Valid values are 'present', 'absent', or 'x.y.z'.
package_manage
Whether to manage the MySQL client package.
Defaults to true
.
package_name
The name of the MySQL client package to install.
Defines
mysql::db
mysql_database { 'information_schema':
ensure => 'present',
charset => 'utf8',
collate => 'utf8_swedish_ci',
}
mysql_database { 'mysql':
ensure => 'present',
charset => 'latin1',
collate => 'latin1_swedish_ci',
}
user
The user for the database you're creating.
password
The password for $user for the database you're creating.
dbname
The name of the database to create.
Defaults to "$name".
charset
The character set for the database.
Defaults to 'utf8'.
collate
The collation for the database.
Defaults to 'utf8_general_ci'.
host
The host to use as part of user@host for grants.
Defaults to 'localhost'.
grant
The privileges to be granted for user@host on the database.
Defaults to 'ALL'.
sql
The path to the sqlfile you want to execute. This can be single file specified as string, or it can be an array of strings.
Defaults to undef
.
enforce_sql
Specifies whether executing the sqlfiles should happen on every run. If set to false, sqlfiles only run once.
Valid values are true
, false
.
Defaults to false
.
ensure
Specifies whether to create the database.
Valid values are 'present', 'absent'.
Defaults to 'present'.
import_timeout
Timeout, in seconds, for loading the sqlfiles.
Defaults to 300.
import_cat_cmd
Command to read the sqlfile for importing the database. Useful for compressed sqlfiles. For example, you can use 'zcat' for .gz files.
Defaults to 'cat'.
Types
mysql_database
mysql_database
creates and manages databases within MySQL.
ensure
Whether the resource is present.
Valid values are 'present', 'absent'.
Defaults to 'present'.
name
The name of the MySQL database to manage.
charset
The CHARACTER SET setting for the database.
Defaults to ':utf8'.
collate
The COLLATE setting for the database.
Defaults to ':utf8_general_ci'.
mysql_user
Creates and manages user grants within MySQL.
mysql_user { 'root@127.0.0.1':
ensure => 'present',
max_connections_per_hour => '0',
max_queries_per_hour => '0',
max_updates_per_hour => '0',
max_user_connections => '0',
}
You can also specify an authentication plugin.
mysql_user{ 'myuser'@'localhost':
ensure => 'present',
plugin => 'unix_socket',
}
TLS options can be specified for a user.
mysql_user{ 'myuser'@'localhost':
ensure => 'present',
tls_options => ['SSL'],
}
name
The name of the user, as 'username@hostname' or username@hostname.
password_hash
The user's password hash of the user. Use mysql_password() for creating such a hash.
max_user_connections
Maximum concurrent connections for the user.
Must be an integer value.
A value of '0' specifies no (or global) limit.
max_connections_per_hour
Maximum connections per hour for the user.
Must be an integer value.
A value of '0' specifies no (or global) limit.
max_queries_per_hour
Maximum queries per hour for the user.
Must be an integer value.
A value of '0' specifies no (or global) limit.
max_updates_per_hour
Maximum updates per hour for the user.
Must be an integer value.
A value of '0' specifies no (or global) limit.
tls_options
SSL-related options for a MySQL account, using one or more tls_option values. 'NONE' specifies that the account has no TLS options enforced, and the available options are 'SSL', 'X509', 'CIPHER cipher', 'ISSUER issuer', 'SUBJECT subject'; as stated in the MySQL documentation.
mysql_grant
mysql_grant
creates grant permissions to access databases within MySQL. To create grant permissions to access databases with MySQL, use it you must create the title of the resource as shown below, following the pattern of username@hostname/database.table
:
mysql_grant { 'root@localhost/*.*':
ensure => 'present',
options => ['GRANT'],
privileges => ['ALL'],
table => '*.*',
user => 'root@localhost',
}
It is possible to specify privileges down to the column level:
mysql_grant { 'root@localhost/mysql.user':
ensure => 'present',
privileges => ['SELECT (Host, User)'],
table => 'mysql.user',
user => 'root@localhost',
}
To revoke GRANT privilege specify ['NONE'].
ensure
Whether the resource is present.
Valid values are 'present', 'absent'.
Defaults to 'present'.
name
Name to describe the grant. Must in a 'user/table' format.
privileges
Privileges to grant the user.
table
The table to which privileges are applied.
user
User to whom privileges are granted.
options
MySQL options to grant. Optional.
mysql_plugin
mysql_plugin
can be used to load plugins into the MySQL Server.
mysql_plugin { 'auth_socket':
ensure => 'present',
soname => 'auth_socket.so',
}
ensure
Whether the resource is present.
Valid values are 'present', 'absent'.
Defaults to 'present'.
name
The name of the MySQL plugin to manage.
soname
The library file name.
mysql_datadir
Initializes the MySQL data directory with version specific code. Pre MySQL 5.7.6 it uses mysql_install_db. After MySQL 5.7.6 it uses mysqld --initialize-insecure.
Insecure initialization is needed, as mysqld version 5.7 introduced 'secure by default' mode. This means MySQL generates a random password and writes it to STDOUT. This means puppet can never access the database server afterwards, as no credentials are available.
This type is an internal type and should not be called directly.
Facts
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 nodes that have only loopback interfaces. Because those nodes aren't connected to the outside world, this shouldn't cause any conflicts.
Limitations
This module has been tested on:
- RedHat Enterprise Linux 5, 6, 7
- Debian 6, 7, 8
- CentOS 5, 6, 7
- Ubuntu 10.04, 12.04, 14.04, 16.04
- Scientific Linux 5, 6
- SLES 11
Testing on other platforms has been minimal and cannot be guaranteed.
Note: The mysqlbackup.sh does not work and is not supported on MySQL 5.7 and greater.
Development
Puppet modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can't access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.
We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
Check out our the complete module contribution guide.
Authors
This module is based on work by David Schmitt. The following contributors have contributed to this module (beyond Puppet Labs):
- Larry Ludwig
- Christian G. Warden
- Daniel Black
- Justin Ellison
- Lowe Schmidt
- Matthias Pigulla
- William Van Hevelingen
- Michael Arnold
- Chris Weyl
- Daniël van Eeden
- Jan-Otto Kröpke
Supported Release 3.11.0
Summary
This release includes README and metadata translations to Japanese, as well as some enhancements and bugfixes.
Added
- New flag for successful backups
- Solaris support improvements
- New parameter
optional_args
for extra innobackupex options - Specify environment variables (e.g. https_proxy) for MySQLTuner download.
- Check to only install bzip2 if
$backupcompress
istrue
- Debian 9 compatibility
- Japanese README
Fixed
- Syntax errors
- Bug where error logs were being created before the datadir was initialized (MODULES-4743)
Supported Release 3.10.0
Summary
This release includes new features for setting TLS options on a mysql user, a new parameter to allow specifying tool to import sql files, as well as various bugfixes.
Features
- (MODULES-3879) Adds
import_cat_cmd
parameter to specify the command to read sql files - Adds support for setting
tls_options
inmysql_user
Bugfixes
- (MODULES-3557) Adds Ubuntu 16.04 package names for language bindings
- (MODULES-3907) Adds MySQL/Percona 5.7 initialize on fresh deploy
Supported Release 3.9.0
Summary
This release adds Percona 5.7 support and compatibility with Ubuntu 16.04, in addition to various bugfixes.
Features
- (MODULES-3441) Adds the
mysqld_version
fact - (MODULES-3513) Adds a new backup dump parameter
maxallowedpacket
- Adds new parameter
xtrabackup_package_name
tomysql::backup::xtrabackup
class - Adds ability to revoke GRANT privilege
Bugfixes
- Fixes a bug where
mysql_user
fails if facter cannot retrieve fqdn. - Fix global parameter usage in backup script
- Adds support for
puppet-staging
version2.0.0
- (MODULES-3601) Moves binary logging configuration to take place after package install
- (MODULES-3711) Add limit to mysql server ID generated value
- (MODULES-3698) Fixes defaults for SLES12
- Updates user name length restrictions for MySQL version 5.7.8 and above.
- Fixes a bug where error log is not writable by owner
Supported Release 3.8.0
Summary
This release adds Percona 5.7 support and compatibility with Ubuntu 16.04, in addition to various bugfixes.
Features
- Adds support for Percona 5.7
- Adds support for Ubuntu 16.04 (Xenial)
Known Limitations
- The mysqlbackup.sh script will not work on MySQL 5.7.0 and up.
Bugfixes
- Use mysql_install_db only with uniq defaults-extra-file
- Updates mysqlbackup.sh to ensure backup directory exist
- Loosen MariaDB recognition to fix it on Debian 8
- Allow mysql::backup::mysqldump to access root_group in tests
- Fixed problem with ignoring parameters from global configs
- Fixes ordering issue that initialized mysqld before config is set
- (MODULES-1256) Fix parameters on OpenSUSE 12
- Fixes install errors on Debian-based OS by configuring the base of includedir
- Configure the configfile location for mariadb
- Default mysqld_type return value should be 'mysql' if another type is not detected
- Make sure that bzip2 is installed before setting up the cron tab job using mysqlbackup.sh
- Fixes path issue on FreeBSD
- Check that /var/lib/mysql actually contains files
- Removes mysql regex when checking type
- (MODULES-2111) Add the system database to user related actions
- Updates default group for logfiles on Debian-based OS to 'adm'
- Fixes an issue with Amazon linux major release 4 installation
- Fixes 'mysql_install_db' script support on Gentoo
- Removes erroneous anchors to mysql::client from mysql::db
- Adds path to be able to find MySQL 5.5 installation on CentOS
Supported Release 3.7.0
Summary
A large release with several new features. Also includes a considerable amount of bugfixes, many around compatibility and improvements to current functionality.
Features
- Now uses mariadb in OpenSuSE >= 13.1.
- Switch to rspec-puppet-facts.
- Additional function to check if table exists before grant.
- Add ability to input password hash directly.
- Now checking major release instead of specific release.
- Debian 8 support.
Bugfixes
- Minor doc update.
- Fixes improper use of function
warn
in backup manifest of server. - Fixes to Compatibility with PE 3.3.
- Fixes
when not managing config file
inmysql_server_spec
. - Improved user validation and munging.
- Fixes fetching the mysql_user password for MySQL >=5.7.6.
- Fixes unique server_id within my.cnf, the issue were the entire mac address was not being read in to generate the id.
- Corrects the daemon_dev_package_name for mariadb on redhat.
- Fix version compare to properly suppress show_diff for root password.
- Fixes to ensure compatibility with future parser.
- Solaris removed from PE in metadata as its not supported.
- Use MYSQL_PWD to avoid mysqldump warnings.
- Use temp cnf file instead of env variable which creates acceptance test failures.
- No longer hash passwords that are already hashed.
- Fix Gemfile to work with ruby 1.8.7.
- Fixed MySQL 5.7.6++ compatibility.
- Fixing error when disabling service management and the service does not exist.
- Ubuntu vivid should use systemd not upstart.
- Fixed new mysql_datadir provider on CentOS for MySQl 5.7.6 compatibility.
- Ensure if service restart to wait till mysql is up.
- Move all dependencies to not have them in case of service unmanaged.
- Re-Added the ability to set a empty string as option parameter.
- Fixes edge-case with dropping pre-existing users with grants.
- Fix logic for choosing rspec version.
- Refactored main acceptance suite.
- Skip idempotency tests on test cells that do have PUP-5016 unfixed.
- Fix tmpdir to be shared across examples.
- Update to current msync configs [006831f].
- Fix mysql_grant with MySQL ANSI_QUOTES mode.
- Generate .my.cnf for all sections.
Supported Release 3.6.2
Summary
Small release for support of newer PE versions. This increments the version of PE in the metadata.json file.
2015-09-22 - Supported Release 3.6.1
Summary
This is a security and bugfix release that fixes incorrect username truncation in the munge for the mysql_user type, incorrect function used in mysql::server::backup
and fixes compatibility issues with PE 3.3.x.
Bugfixes
- Loosen the regex in mysql_user munging so the username is not unintentionally truncated.
- Use
warning()
notwarn()
- Metadata had inadvertantly dropped 3.3.x support
- Some 3.3.x compatibility issues in
mysqltuner
were corrected
2015-08-10 - Supported Release 3.6.0
Summary
This release adds the ability to use mysql::db and mysql_*
types against unmanaged or external mysql instances.
Features
- Add ability to use mysql::db WITHOUT mysql::server (ie, externally)
- Add prescript attribute to mysql::server::backup for xtrabackup
- Add postscript ability to xtrabackup provider.
Bugfixes
- Fix default root passwords blocking puppet on mysql 5.8
- Fix service dependency when package_manage is false
- Fix selinux permissions on my.cnf
2015-07-23 - Supported Release 3.5.0
Summary
A small release to add explicit support to newer Puppet versions and accumulated patches.
Features/Improvements
- Start running tests against puppet 4
- Support longer usernames on newer MariaDB versions
- Add parameters for Solaris 11 and 12
Bugfixes
- Fix references to the mysql-server package
- mysql_server_id doesn't throw and error on machines without macaddress
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.
Features
- Add package_manage parameters to
mysql::server
andmysql::client
(MODULES-1143) - README improvements
- Add
mysqldump
,mysqlbackup
, andxtrabackup
backup providers.
Bugfixes
- log-error overrides were not being properly used (MODULES-1804)
- check for full path for log-bin to stop puppet from managing file '.'
2015-02-09 - Supported Release 3.2.0
Summary
This release includes several new features and bugfixes, including support for various plugins, making the output from mysql_password more consistent when input is empty and improved username validation.
Features
- Add type and provider to manage plugins
- Add support for authentication plugins
- Add support for mysql_install_db on freebsd
- Add
create_root_user
andcreate_root_my_cnf
parameters tomysql::server
Bugfixes
- Remove dependency on stdlib >= 4.1.0 (MODULES-1759)
- Make grant autorequire user
- Remove invalid parameter 'provider' from mysql_user instance (MODULES-1731)
- Return empty string for empty input in mysql_password
- Fix
mysql::account_security
when fqdn==localhost - Update username validation (MODULES-1520)
- Future parser fix in params.pp
- Fix package name for debian 8
- Don't start the service until the server package is installed and the config file is in place
- Test fixes
- Lint fixes
2014-12-16 - Supported Release 3.1.0
Summary
This release includes several new features, including SLES12 support, and a number of bug fixes.
Notes
mysql::server::mysqltuner
has been refactored to fetch the mysqltuner script from github by default. If you are running on a non-network-connected system, you will need to download that file and have it available to your node at a path specified by the source
parameter to the mysqltuner
class.
Features
- Add support for install_options for all package resources (MODULES-1484)
- Add log-bin directory creation
- Allow mysql::db to import multiple files (MODULES-1338)
- SLES12 support
- Improved identifier quoting detections
- Reworked
mysql::server::mysqltuner
so that we are no longer packaging the script as it is licensed under the GPL.
Bugfixes
- Fix regression in username validation
- Proper containment for mysql::client in mysql::db
- Support quoted usernames of length 15 and 16 chars
2014-11-11 - Supported Release 3.0.0
Summary
Added several new features including MariaDB support and future parser
Backwards-incompatible Changes
- Remove the deprecated
database
,database_user
, anddatabase_grant
resources. The correct resources to use aremysql
,mysql_user
, andmysql_grant
respectively.
Features
- Add MariaDB Support
- The mysqltuner perl script has been updated to 1.3.0 based on work at http://github.com/major/MySQLTuner-perl
- Add future parse support, fixed issues with undef to empty string
- Pass the backup credentials to 'SHOW DATABASES'
- Ability to specify the Includedir for
mysql::server
mysql::db
now has an import_timeout feature that defaults to 300- The
mysql
class has been removed mysql::server
now takes anoverride_options
hash that will affect the installation- Ability to install both dev and client dev
BugFix
mysql::server::backup
now passesensure
param to the nestedmysql_grant
mysql::server::service
now properly requires the presence of thelog_error
filemysql::config
now occurs beforemysql::server::install_db
correctly
2014-07-15 - Supported Release 2.3.1
Summary
This release merely updates metadata.json so the module can be uninstalled and upgraded via the puppet module command.
2014-05-14 - Supported Release 2.3.0
This release primarily adds support for RHEL7 and Ubuntu 14.04 but it also adds a couple of new parameters to allow for further customization, as well as ensuring backups can backup stored procedures properly.
Features
Added execpath
to allow a custom executable path for non-standard mysql installations.
Added dbname
to mysql::db and use ensure_resource to create the resource.
Added support for RHEL7 and Fedora Rawhide.
Added support for Ubuntu 14.04.
Create a warning for if you disable SSL.
Ensure the error logfile is owned by MySQL.
Disable ssl on FreeBSD.
Add PROCESS privilege for backups.
Bugfixes
Known Bugs
- No known bugs
2014-03-04 - Supported Release 2.2.3
Summary
This is a supported release. This release removes a testing symlink that can cause trouble on systems where /var is on a seperate filesystem from the modulepath.
Features
Bugfixes
Known Bugs
- No known bugs
2014-03-04 - Supported Release 2.2.2
Summary
This is a supported release. Mostly comprised of enhanced testing, plus a bugfix for Suse.
Bugfixes
- PHP bindings on Suse
- Test fixes
Known Bugs
- No known bugs
2014-02-19 - Version 2.2.1
Summary
Minor release that repairs mysql_database{} so that it sees the correct collation settings (it was only checking the global mysql ones, not the actual database and constantly setting it over and over since January 22nd).
Also fixes a bunch of tests on various platforms.
2014-02-13 - Version 2.2.0
Summary
Features
- Add
backupdirmode
,backupdirowner
,backupdirgroup
to mysql::server::backup to allow customizing the mysqlbackupdir. - Support multiple options of the same name, allowing you to do 'replicate-do-db' => ['base1', 'base2', 'base3'] in order to get three lines of replicate-do-db = base1, replicate-do-db = base2 etc.
Bugfixes
- Fix
restart
so it actually stops mysql restarting if set to false. - DRY out the defaults_file functionality in the providers.
- mysql_grant fixed to work with root@localhost/@.
- mysql_grant fixed for WITH MAX_QUERIES_PER_HOUR
- mysql_grant fixed so revoking all privileges accounts for GRANT OPTION
- mysql_grant fixed to remove duplicate privileges.
- mysql_grant fixed to handle PROCEDURES when removing privileges.
- mysql_database won't try to create existing databases, breaking replication.
- bind_address renamed bind-address in 'mysqld' options.
- key_buffer renamed to key_buffer_size.
- log_error renamed to log-error.
- pid_file renamed to pid-file.
- Ensure mysql::server:root_password runs before mysql::server::backup
- Fix options_override -> override_options in the README.
- Extensively rewrite the README to be accurate and awesome.
- Move to requiring stdlib 3.2.0, shipped in PE3.0
- Add many new tests.
2013-11-13 - Version 2.1.0
Summary
The most important changes in 2.1.0 are improvements to the my.cnf creation, as well as providers. Setting options to = true strips them to be just the key name itself, which is required for some options.
The provider updates fix a number of bugs, from lowercase privileges to deprecation warnings.
Last, the new hiera integration functionality should make it easier to externalize all your grants, users, and, databases. Another great set of community submissions helped to make this release.
Features
- Some options can not take a argument. Gets rid of the '= true' when an option is set to true.
- Easier hiera integration: Add hash parameters to mysql::server to allow specifying grants, users, and databases.
Bugfixes
- Fix an issue with lowercase privileges in mysql_grant{} causing them to be reapplied needlessly.
- Changed defaults-file to defaults-extra-file in providers.
- Ensure /root/.my.cnf is 0600 and root owned.
- database_user deprecation warning was incorrect.
- Add anchor pattern for client.pp
- Documentation improvements.
- Various test fixes.
2013-10-21 - Version 2.0.1
Summary
This is a bugfix release to handle an issue where unsorted mysql_grant{} privileges could cause Puppet to incorrectly reapply the permissions on each run.
Bugfixes
- Mysql_grant now sorts privileges in the type and provider for comparison.
- Comment and test tweak for PE3.1.
2013-10-14 - Version 2.0.0
Summary
(Previously detailed in the changelog for 2.0.0-rc1)
This module has been completely refactored and works significantly different. The changes are broad and touch almost every piece of the module.
See the README.md for full details of all changes and syntax. Please remain on 1.0.0 if you don't have time to fully test this in dev.
- mysql::server, mysql::client, and mysql::bindings are the primary interface classes.
- mysql::server takes an
override_options
parameter to set my.cnf options, with the hash format: { 'section' => { 'thing' => 'value' }} - mysql attempts backwards compatibility by forwarding all parameters to mysql::server.
2013-10-09 - Version 2.0.0-rc5
Summary
Hopefully the final rc! Further fixes to mysql_grant (stripping out the cleverness so we match a much wider range of input.)
Bugfixes
- Make mysql_grant accept '.'@'.' in terms of input for user@host.
2013-10-09 - Version 2.0.0-rc4
Summary
Bugfixes to mysql_grant and mysql_user form the bulk of this rc, as well as ensuring that values in the override_options hash that contain a value of '' are created as just "key" in the conf rather than "key =" or "key = false".
Bugfixes
- Improve mysql_grant to work with IPv6 addresses (both long and short).
- Ensure @host users work as well as user@host users.
- Updated my.cnf template to support items with no values.
2013-10-07 - Version 2.0.0-rc3
Summary
Fix mysql::server::monitor's use of mysql_user{}.
Bugfixes
- Fix myql::server::monitor's use of mysql_user{} to grant the proper permissions. Add specs as well. (Thanks to treydock!)
2013-10-03 - Version 2.0.0-rc2
Summary
Bugfixes
Bugfixes
- Fix a duplicate parameter in mysql::server
2013-10-03 - Version 2.0.0-rc1
Summary
This module has been completely refactored and works significantly different. The changes are broad and touch almost every piece of the module.
See the README.md for full details of all changes and syntax. Please remain on 1.0.0 if you don't have time to fully test this in dev.
- mysql::server, mysql::client, and mysql::bindings are the primary interface classes.
- mysql::server takes an
override_options
parameter to set my.cnf options, with the hash format: { 'section' => { 'thing' => 'value' }} - mysql attempts backwards compatibility by forwarding all parameters to mysql::server.
2013-09-23 - Version 1.0.0
Summary
This release introduces a number of new type/providers, to eventually replace the database_ ones. The module has been converted to call the new providers rather than the previous ones as they have a number of fixes, additional options, and work with puppet resource.
This 1.0.0 release precedes a large refactoring that will be released almost immediately after as 2.0.0.
Features
- Added mysql_grant, mysql_database, and mysql_user.
- Add
mysql::bindings
class and refactor all other bindings to be contained underneath mysql::bindings:: namespace. - Added support to back up specified databases only with 'mysqlbackup' parameter.
- Add option to mysql::backup to set the backup script to perform a mysqldump on each database to its own file
Bugfixes
- Update my.cnf.pass.erb to allow custom socket support
- Add environment variable for .my.cnf in mysql::db.
- Add HOME environment variable for .my.cnf to mysqladmin command when (re)setting root password
2013-07-15 - Version 0.9.0
Features
- Add
mysql::backup::backuprotate
parameter - Add
mysql::backup::delete_before_dump
parameter - Add
max_user_connections
attribute todatabase_user
type
Bugfixes
- Add client package dependency for
mysql::db
- Remove duplicate
expire_logs_days
andmax_binlog_size
settings - Make root's
.my.cnf
file path dynamic - Update pidfile path for Suse variants
- Fixes for lint
2013-07-05 - Version 0.8.1
Bugfixes
- Fix a typo in the Fedora 19 support.
2013-07-01 - Version 0.8.0
Features
- mysql::perl class to install perl-DBD-mysql.
- minor improvements to the providers to improve reliability
- Install the MariaDB packages on Fedora 19 instead of MySQL.
- Add new
mysql
class parameters:max_connections
: The maximum number of allowed connections.manage_config_file
: Opt out of puppetized control of my.cnf.ft_min_word_len
: Fine tune the full text search.ft_max_word_len
: Fine tune the full text search.
- Add new
mysql
class performance tuning parameters:key_buffer
thread_stack
thread_cache_size
myisam-recover
query_cache_limit
query_cache_size
max_connections
tmp_table_size
table_open_cache
long_query_time
- Add new
mysql
class replication parameters:server_id
sql_log_bin
log_bin
max_binlog_size
binlog_do_db
expire_logs_days
log_bin_trust_function_creators
replicate_ignore_table
replicate_wild_do_table
replicate_wild_ignore_table
expire_logs_days
max_binlog_size
Bugfixes
- No longer restart MySQL when /root/.my.cnf changes.
- Ensure mysql::config runs before any mysql::db defines.
2013-06-26 - Version 0.7.1
Bugfixes
- Single-quote password for special characters
- Update travis testing for puppet 3.2.x and missing Bundler gems
2013-06-25 - Version 0.7.0
This is a maintenance release for community bugfixes and exposing configuration variables.
- Add new
mysql
class parameters:basedir
: The base directory mysql usesbind_address
: The IP mysql binds toclient_package_name
: The name of the mysql client packageconfig_file
: The location of the server config fileconfig_template
: The template to use to generate my.cnfdatadir
: The directory MySQL's datafiles are storeddefault_engine
: The default engine to use for tablesetc_root_password
: Whether or not to add the mysql root password to /etc/my.cnfjava_package_name
: The name of the java package containing the java connectorlog_error
: Where to log errorsmanage_service
: Boolean dictating if mysql::server should manage the servicemax_allowed_packet
: Maximum network packet size mysqld will acceptold_root_password
: Previous root user passwordphp_package_name
: The name of the phpmysql package to installpidfile
: The location mysql will expect the pidfile to beport
: The port mysql listens onpurge_conf_dir
: Value fed to recurse and purge parameters of the /etc/mysql/conf.d resourcepython_package_name
: The name of the python mysql package to installrestart
: Whether to restart mysqldroot_group
: Use specified group for root-owned filesroot_password
: The root MySQL password to useruby_package_name
: The name of the ruby mysql package to installruby_package_provider
: The installation suite to use when installing the ruby packageserver_package_name
: The name of the server package to installservice_name
: The name of the service to startservice_provider
: The name of the service providersocket
: The location of the MySQL server socket filessl_ca
: The location of the SSL CA Certssl_cert
: The location of the SSL Certificate to usessl_key
: The SSL key to usessl
: Whether or not to enable ssltmpdir
: The directory MySQL's tmpfiles are stored
- Deprecate
mysql::package_name
parameter in favor ofmysql::client_package_name
- Fix local variable template deprecation
- Fix dependency ordering in
mysql::db
- Fix ANSI quoting in queries
- Fix travis support (but still messy)
- Fix typos
2013-01-11 - Version 0.6.1
- Fix providers when /root/.my.cnf is absent
2013-01-09 - Version 0.6.0
- Add
mysql::server::config
define for specific config directives - Add
mysql::php
class for php support - Add
backupcompress
parameter tomysql::backup
- Add
restart
parameter tomysql::config
- Add
purge_conf_dir
parameter tomysql::config
- Add
manage_service
parameter tomysql::server
- Add syslog logging support via the
log_error
parameter - Add initial SuSE support
- Fix remove non-localhost root user when fqdn != hostname
- Fix dependency in
mysql::server::monitor
- Fix .my.cnf path for root user and root password
- Fix ipv6 support for users
- Fix / update various spec tests
- Fix typos
- Fix lint warnings
2012-08-23 - Version 0.5.0
- Add puppetlabs/stdlib as requirement
- Add validation for mysql privs in provider
- Add
pidfile
parameter to mysql::config - Add
ensure
parameter to mysql::db - Add Amazon linux support
- Change
bind_address
parameter to be optional in my.cnf template - Fix quoting root passwords
2012-07-24 - Version 0.4.0
- Fix various bugs regarding database names
- FreeBSD support
- Allow specifying the storage engine
- Add a backup class
- Add a security class to purge default accounts
2012-05-03 - Version 0.3.0
- 14218 Query the database for available privileges
- Add mysql::java class for java connector installation
- Use correct error log location on different distros
- Fix set_mysql_rootpw to properly depend on my.cnf
2012-04-11 - Version 0.2.0
2012-03-19 - William Van Hevelingen blkperl@cat.pdx.edu
- (#13203) Add ssl support (f7e0ea5)
2012-03-18 - Nan Liu nan@puppetlabs.com
- Travis ci before script needs success exit code. (0ea463b)
2012-03-18 - Nan Liu nan@puppetlabs.com
- Fix Puppet 2.6 compilation issues. (9ebbbc4)
2012-03-16 - Nan Liu nan@puppetlabs.com
- Add travis.ci for testing multiple puppet versions. (33c72ef)
2012-03-15 - William Van Hevelingen blkperl@cat.pdx.edu
- (#13163) Datadir should be configurable (f353fc6)
2012-03-16 - Nan Liu nan@puppetlabs.com
- Document create_resources dependency. (558a59c)
2012-03-16 - Nan Liu nan@puppetlabs.com
- Fix spec test issues related to error message. (eff79b5)
2012-03-16 - Nan Liu nan@puppetlabs.com
- Fix mysql service on Ubuntu. (72da2c5)
2012-03-16 - Dan Bode dan@puppetlabs.com
- Add more spec test coverage (55e399d)
2012-03-16 - Nan Liu nan@puppetlabs.com
- (#11963) Fix spec test due to path changes. (1700349)
2012-03-07 - François Charlier fcharlier@ploup.net
- Add a test to check path for 'mysqld-restart' (b14c7d1)
2012-03-07 - François Charlier fcharlier@ploup.net
- Fix path for 'mysqld-restart' (1a9ae6b)
2012-03-15 - Dan Bode dan@puppetlabs.com
- Add rspec-puppet tests for mysql::config (907331a)
2012-03-15 - Dan Bode dan@puppetlabs.com
- Moved class dependency between sever and config to server (da62ad6)
2012-03-14 - Dan Bode dan@puppetlabs.com
- Notify mysql restart from set_mysql_rootpw exec (0832a2c)
2012-03-15 - Nan Liu nan@puppetlabs.com
- Add documentation related to osfamily fact. (8265d28)
2012-03-14 - Dan Bode dan@puppetlabs.com
- Mention osfamily value in failure message (e472d3b)
2012-03-14 - Dan Bode dan@puppetlabs.com
- Fix bug when querying for all database users (015490c)
2012-02-09 - Nan Liu nan@puppetlabs.com
- Major refactor of mysql module. (b1f90fd)
2012-01-11 - Justin Ellison justin.ellison@buckle.com
- Ruby and Python's MySQL libraries are named differently on different distros. (1e926b4)
2012-01-11 - Justin Ellison justin.ellison@buckle.com
- Per @ghoneycutt, we should fail explicitly and explain why. (09af083)
2012-01-11 - Justin Ellison justin.ellison@buckle.com
- Removing duplicate declaration (7513d03)
2012-01-10 - Justin Ellison justin.ellison@buckle.com
- Use socket value from params class instead of hardcoding. (663e97c)
2012-01-10 - Justin Ellison justin.ellison@buckle.com
- Instead of hardcoding the config file target, pull it from mysql::params (031a47d)
2012-01-10 - Justin Ellison justin.ellison@buckle.com
- Moved $socket to within the case to toggle between distros. Added a $config_file variable to allow per-distro config file destinations. (360eacd)
2012-01-10 - Justin Ellison justin.ellison@buckle.com
- Pretty sure this is a bug, 99% of Linux distros out there won't ever hit the default. (3462e6b)
2012-02-09 - William Van Hevelingen blkperl@cat.pdx.edu
- Changed the README to use markdown (3b7dfeb)
2012-02-04 - Daniel Black grooverdan@users.sourceforge.net
- (#12412) mysqltuner.pl update (b809e6f)
2011-11-17 - Matthias Pigulla mp@webfactory.de
- (#11363) Add two missing privileges to grant: event_priv, trigger_priv (d15c9d1)
2011-12-20 - Jeff McCune jeff@puppetlabs.com
- (minor) Fixup typos in Modulefile metadata (a0ed6a1)
2011-12-19 - Carl Caum carl@carlcaum.com
- Only notify Exec to import sql if sql is given (0783c74)
2011-12-19 - Carl Caum carl@carlcaum.com
- (#11508) Only load sql_scripts on DB creation (e3b9fd9)
2011-12-13 - Justin Ellison justin.ellison@buckle.com
- Require not needed due to implicit dependencies (3058feb)
2011-12-13 - Justin Ellison justin.ellison@buckle.com
- Bug #11375: puppetlabs-mysql fails on CentOS/RHEL (a557b8d)
2011-06-03 - Dan Bode dan@puppetlabs.com - 0.0.1
- initial commit
Dependencies
- puppetlabs/stdlib (>= 3.2.0 < 5.0.0)
- puppet/staging (>= 1.0.1 < 3.0.0)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.