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

24 lines
651 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
#
class mysql::server::root_password {
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
# manage root password if it is set
Add new parameters create_root_user and create_root_my_cnf. This allows the galera module and others to write ${::root_home}/.my.cnf independently from create the mysql user. This is useful for cluster setups where you want to create ${::root_home}/.my.cnf on every node but create the user only once.
2014-10-06 10:53:30 +02:00
if $mysql::server::create_root_user == true and $mysql::server::root_password != 'UNSET' {
Add mysql::globals and refactor mysql::server. This work adds a new mysql::globals class which contains a hash used to build my.cnf from. It's used to share this data across multiple classes so that the client and server can share this data. End users can modify content in my.cnf by including mysql::globals and passing in override_options as a hash that looks like: override_options = { 'mysqld' => { 'max_connections' => '120' } } This completely replaces the mess of parameters that existed in the main mysql class before. Completely refactor mysql::server and rework the API. This changes ordering, changes from execs{} to mysql_user for the root password, removes some functionality (like the etc_root_password), and generally makes some tough decisions about how mysql::server should be built.
2013-09-13 19:04:42 +02:00
mysql_user { 'root@localhost':
ensure => present,
password_hash => mysql_password($mysql::server::root_password),
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
}
Add new parameters create_root_user and create_root_my_cnf. This allows the galera module and others to write ${::root_home}/.my.cnf independently from create the mysql user. This is useful for cluster setups where you want to create ${::root_home}/.my.cnf on every node but create the user only once.
2014-10-06 10:53:30 +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
Add new parameters create_root_user and create_root_my_cnf. This allows the galera module and others to write ${::root_home}/.my.cnf independently from create the mysql user. This is useful for cluster setups where you want to create ${::root_home}/.my.cnf on every node but create the user only once.
2014-10-06 10:53:30 +02:00
if $mysql::server::create_root_my_cnf == true and $mysql::server::root_password != 'UNSET' {
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 { "${::root_home}/.my.cnf":
content => template('mysql/my.cnf.pass.erb'),
Fix owner -> user typo.
2013-11-06 17:36:55 +01:00
owner => 'root',
ensure /root/.my.cnf is 0600 and root owned explicitly set /root/.my.cnf's owner and mode to ensure it will be created with as root owned and 0600. This change fixes #357
2013-11-05 19:56:27 +01:00
mode => '0600',
Add mysql::globals and refactor mysql::server. This work adds a new mysql::globals class which contains a hash used to build my.cnf from. It's used to share this data across multiple classes so that the client and server can share this data. End users can modify content in my.cnf by including mysql::globals and passing in override_options as a hash that looks like: override_options = { 'mysqld' => { 'max_connections' => '120' } } This completely replaces the mess of parameters that existed in the main mysql class before. Completely refactor mysql::server and rework the API. This changes ordering, changes from execs{} to mysql_user for the root password, removes some functionality (like the etc_root_password), and generally makes some tough decisions about how mysql::server should be built.
2013-09-13 19:04:42 +02:00
require => Mysql_user['root@localhost'],
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
}
}
}
Reference in a new issue Copy permalink