Todd Courtnage
2013-Oct-08 00:05 UTC
[Puppet Users] How to properly override manage_config_file parameter in puppetlabs-mysql module?
I''ve been using puppet for a while, and have built up quite a range of my own very (very!) basic modules to do what I need to do. Now I''m starting to delve into the world of puppetlabs and am testing the new puppetlabs-mysql module (2.0.0-rc3) and have a (probably) fairly basic question, about parameters and overriding them. I don''t want the module to manage the MySQL configuration file (which I think is a dangerous default in the module, but that''s something else). I''m using puppet dashboard, and was hoping I could simply add a parameter (manage_config_file = false) to the node via the puppet dashboard, but that is not working. What is the best/proper way to override the manage_config_file parameter in mysql::server? I could change the $manage_config_file from true to false in the mysql::params class, but I believe that will break upgrades to the module when doing a "puppet module upgrade puppetlabs-mysql", so that''s not ideal. Puppet 3.2.1 Puppet Dashboard 1.2.23 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Seemingly Similar Threads
- Announce: Puppet Dashboard 1.2.23-rc3 Available
- Announce: Puppet Dashboard 1.2.23 Available
- Puppet dashboard - having cached catalog runs show up as warnings
- Puppet Dashboard Error 400 Invalid Parameter at passenger pp:48
- Announce: Puppet Dashboard 1.2.13-rc1 Available