Version information
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-mysql', '2.2.1'
Learn more about managing modules with a PuppetfileDocumentation
#MySQL
####Table of Contents
- Overview
- 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
##Overview
The mysql module installs, configures, and manages the MySQL service.
##Module Description
The mysql module manages both the installation and configuration of MySQL as well as extends Puppet to allow management of MySQL resources, such as databases, users, and grants.
##Backwards Compatibility
This module has just undergone a very large rewrite. Some new classes have been added, and many previous classes and configurations work differently than before. We've attempted to handle backwards compatibility automatically by adding a
attempt_compatibility_mode
parameter to the main mysql class. If you set
this to 'true' it will attempt to map your previous parameters into the new
mysql::server
class.
#####WARNING
Compatibility mode may fail. It may eat your MySQL server. PLEASE test it before running it live, even if the test is just a no-op and manual comparison. Please be careful!
##Setup
###What MySQL affects
- MySQL package
- MySQL configuration files
- MySQL service
###Beginning with MySQL
If you just want a server installed with the default options you can run
include '::mysql::server'
.
If you need to customize options, such as the root
password or /etc/my.cnf
settings, then you must also pass in an override hash:
class { '::mysql::server':
root_password => 'strongpassword',
override_options => { 'mysqld' => { 'max_connections' => '1024' } }
}
##Usage
All interaction for the server is done via mysql::server
. To install the
client you use mysql::client
, and to install bindings you can use
mysql::bindings
.
###Overrides
The hash structure for overrides in mysql::server
is as follows:
$override_options = {
'section' => {
'item' => 'thing',
}
}
For items that you would traditionally represent as:
You can just make an entry like thing => true
, thing => value
, or thing => "
in the hash. You can also pass an array thing => ['value', 'value2']
or even list each thing => value
separately on separate lines. MySQL doesn't care if 'thing' is alone or set to a value; it'll happily accept both. To keep an option out of the my.cnf file, e.g. when using override_options to revert to a default value, you can pass thing => undef.
If an option needs multiple instances, you can pass an array. For example
$override_options = {
'mysqld' => {
'replicate-do-db' => ['base1', 'base2'],
}
}
will produce
###Custom configuration
To add custom MySQL configuration, drop additional files into
/etc/mysql/conf.d/
. Dropping files into conf.d allows you to override settings or add additional ones, which is helpful if you choose not to use override_options
in mysql::server
. The conf.d location is hardcoded into the my.cnf template file.
##Reference
###Classes
####Public classes
mysql::server
: Installs and configures MySQL.mysql::server::account_security
: Deletes default MySQL accounts.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::config
: Configures MYSQL.mysql::server::service
: Manages service.mysql::server::root_password
: Sets MySQL root password.mysql::server::providers
: Creates users, grants, and databases.mysql::bindings::java
: Installs Java bindings.mysql::bindings::perl
: Installs Perl bindings.mysql::bindings::python
: Installs Python bindings.mysql::bindings::ruby
: Installs Ruby bindings.mysql::client::install
: Installs MySQL client.
###Parameters
####mysql::server
#####root_password
The MySQL root password. Puppet will attempt to set the root password and update /root/.my.cnf
with it.
#####old_root_password
The previous root password (REQUIRED if you wish to change the root password via Puppet.)
#####override_options
The hash of override options to pass into MySQL. It can be structured like a hash in the my.cnf file, so entries look like
$override_options = {
'section' => {
'item' => 'thing',
}
}
For items that you would traditionally represent as:
You can just make an entry like thing => true
, thing => value
, or thing => "
in the hash. You can also pass an array thing => ['value', 'value2']
or even list each thing => value
separately on separate lines. MySQL doesn't care if 'thing' is alone or set to a value; it'll happily accept both. To keep an option out of the my.cnf file, e.g. when using override_options to revert to a default value, you can pass thing => undef.
#####config_file
The location of the MySQL configuration file.
#####manage_config_file
Whether the MySQL configuration file should be managed.
#####purge_conf_dir
Whether the conf.d directory should be purged.
#####restart
Whether the service should be restarted when things change.
#####root_group
What is the group used for root?
#####package_ensure
What to set the package to. Can be 'present', 'absent', or 'x.y.z'.
#####package_name
The name of the mysql server package to install.
#####remove_default_accounts
Boolean to decide if we should automatically include
mysql::server::account_security
.
#####service_enabled
Boolean to decide if the service should be enabled.
#####service_manage
Boolean to decide if the service should be managed.
#####service_name
The name of the mysql server service.
#####service_provider
The provider to use to manage the service.
#####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',
},
}
#####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 to back up into.
#####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
Boolean to determine if backups should be compressed.
#####backuprotate
How many days to keep backups for.
#####delete_before_dump
Boolean to determine if you should cleanup before backing up or after.
#####backupdatabases
Array of databases to specifically back up.
#####file_per_database
Whether a separate file be used per database.
#####ensure
Allows you to remove the backup scripts. Can be 'present' or 'absent'.
#####time
An array of two elements to set the backup time. Allows ['23', '5'] or ['3', '45'] for HH:MM times.
#####postscript
A script that is executed at when the backup is finished. This could be used to (r)sync the backup to a central store. This script can be either a single line that is directly executed or a number of lines, when supplied as an array. It could also be one or more externally managed (executable) files.
####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 to allow to access the MySQL monitoring user.
####mysql::bindings
#####java_enable
Boolean to decide if the Java bindings should be installed.
#####perl_enable
Boolean to decide if the Perl bindings should be installed.
#####php_enable
Boolean to decide if the PHP bindings should be installed.
#####python_enable
Boolean to decide if the Python bindings should be installed.
#####ruby_enable
Boolean to decide if the Ruby bindings should be installed.
#####java_package_ensure
What to set the package to. Can be 'present', 'absent', or 'x.y.z'.
#####java_package_name
The name of the package to install.
#####java_package_provider
What provider should be used to install the package.
#####perl_package_ensure
What to set the package to. Can be 'present', 'absent', or 'x.y.z'.
#####perl_package_name
The name of the package to install.
#####perl_package_provider
What provider should be used to install the package.
#####python_package_ensure
What to set the package to. Can be 'present', 'absent', or 'x.y.z'.
#####python_package_name
The name of the package to install.
#####python_package_provider
What provider should be used to install the package.
#####ruby_package_ensure
What to set the package to. Can be 'present', 'absent', or 'x.y.z'.
#####ruby_package_name
The name of the package to install.
#####ruby_package_provider
What provider should be used to install the package.
####mysql::client
#####bindings_enable
Boolean to automatically install all bindings.
#####package_ensure
What to set the package to. Can be 'present', 'absent', or 'x.y.z'.
#####package_name
What is the name of the mysql client package to install.
###Defines
####mysql::db
Creates a database with a user and assigns some privileges.
mysql::db { 'mydb':
user => 'myuser',
password => 'mypass',
host => 'localhost',
grant => ['SELECT', 'UPDATE'],
}
###Providers
####mysql_database
mysql_database
can be used to create and manage databases within MySQL.
mysql_database { 'information_schema':
ensure => 'present',
charset => 'utf8',
collate => 'utf8_swedish_ci',
}
mysql_database { 'mysql':
ensure => 'present',
charset => 'latin1',
collate => 'latin1_swedish_ci',
}
####mysql_user
mysql_user
can be used to create and manage 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',
}
####mysql_grant
mysql_grant
can be used to create grant permissions to access databases within
MySQL. To 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',
}
##Limitations
This module has been tested on:
- RedHat Enterprise Linux 5/6
- Debian 6/7
- CentOS 5/6
- Ubuntu 12.04
Testing on other platforms has been light and cannot be guaranteed.
#Development
Puppet Labs 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.
You can read the complete module contribution guide on the Puppet Labs wiki.
Authors
This module is based on work by David Schmitt. The following contributors have contributed patches 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
Types in this module release
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.
Fixes:
- 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.
Fixes:
- 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.)
Fixes:
- 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".
Fixes:
- 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{}.
Fixes:
- 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
Fixes:
- 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)
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 2013 Puppet Labs 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.