opuppet/module-puppetlabs-mysql
5
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
module-puppetlabs-mysql/manifests/server/config.pp

31 lines
618 B
ObjectPascal
Raw Normal View History

Refactor to use mysql::globals. This initial round of work focuses on adding the concept of mysql::globals to the module. This is a shared place to provide all the data the module needs, and then clients, servers, and providers can all rely on this information to set things up. This is being primarily used at first to allow a default_options hash that contains all the previous parameters and takes a overrides_options that allows you to then further customize any of the options in my.cnf.
2013-09-09 17:34:39 +02:00
# See README.me for options.
class mysql::server::config {
New configuration define. * added a define to easily create .cnf files in /etc/mysql/conf.d/ * fix wrong path for .my.cnf in /etc/
2012-08-13 10:59:28 +02:00
Remove mysql::globals. This turned out to be a fairly bad idea. It begun as a way to try and mirror what happens in the postgresql module for consistency but instead made things complex. I've changed it to have the override_options in mysql::server which leads much more naturally out of the design and shape of MySQL.
2013-09-25 00:04:29 +02:00
$options = $mysql::server::options
Refactor to use mysql::globals. This initial round of work focuses on adding the concept of mysql::globals to the module. This is a shared place to provide all the data the module needs, and then clients, servers, and providers can all rely on this information to set things up. This is being primarily used at first to allow a default_options hash that contains all the previous parameters and takes a overrides_options that allows you to then further customize any of the options in my.cnf.
2013-09-09 17:34:39 +02:00
File {
owner => 'root',
Remove mysql::globals. This turned out to be a fairly bad idea. It begun as a way to try and mirror what happens in the postgresql module for consistency but instead made things complex. I've changed it to have the override_options in mysql::server which leads much more naturally out of the design and shape of MySQL.
2013-09-25 00:04:29 +02:00
group => $mysql::server::root_group,
Refactor to use mysql::globals. This initial round of work focuses on adding the concept of mysql::globals to the module. This is a shared place to provide all the data the module needs, and then clients, servers, and providers can all rely on this information to set things up. This is being primarily used at first to allow a default_options hash that contains all the previous parameters and takes a overrides_options that allows you to then further customize any of the options in my.cnf.
2013-09-09 17:34:39 +02:00
mode => '0400',
}
file { '/etc/mysql':
ensure => directory,
mode => '0755',
New configuration define. * added a define to easily create .cnf files in /etc/mysql/conf.d/ * fix wrong path for .my.cnf in /etc/
2012-08-13 10:59:28 +02:00
}
Refactor to use mysql::globals. This initial round of work focuses on adding the concept of mysql::globals to the module. This is a shared place to provide all the data the module needs, and then clients, servers, and providers can all rely on this information to set things up. This is being primarily used at first to allow a default_options hash that contains all the previous parameters and takes a overrides_options that allows you to then further customize any of the options in my.cnf.
2013-09-09 17:34:39 +02:00
file { '/etc/mysql/conf.d':
ensure => directory,
mode => '0755',
Remove mysql::globals. This turned out to be a fairly bad idea. It begun as a way to try and mirror what happens in the postgresql module for consistency but instead made things complex. I've changed it to have the override_options in mysql::server which leads much more naturally out of the design and shape of MySQL.
2013-09-25 00:04:29 +02:00
recurse => $mysql::server::purge_conf_dir,
purge => $mysql::server::purge_conf_dir,
New configuration define. * added a define to easily create .cnf files in /etc/mysql/conf.d/ * fix wrong path for .my.cnf in /etc/
2012-08-13 10:59:28 +02:00
}
Remove mysql::globals. This turned out to be a fairly bad idea. It begun as a way to try and mirror what happens in the postgresql module for consistency but instead made things complex. I've changed it to have the override_options in mysql::server which leads much more naturally out of the design and shape of MySQL.
2013-09-25 00:04:29 +02:00
if $mysql::server::manage_config_file {
file { $mysql::server::config_file:
Refactor to use mysql::globals. This initial round of work focuses on adding the concept of mysql::globals to the module. This is a shared place to provide all the data the module needs, and then clients, servers, and providers can all rely on this information to set things up. This is being primarily used at first to allow a default_options hash that contains all the previous parameters and takes a overrides_options that allows you to then further customize any of the options in my.cnf.
2013-09-09 17:34:39 +02:00
content => template('mysql/my.cnf.erb'),
mode => '0644',
New configuration define. * added a define to easily create .cnf files in /etc/mysql/conf.d/ * fix wrong path for .my.cnf in /etc/
2012-08-13 10:59:28 +02:00
}
}
}
Reference in a new issue Copy permalink