[Puppet Users] mysql module package names

Hi, Is there any better approach to handle mysql package names with different flavors ? In the current forge module, we need to pass package name. Is there any better approach to deriving package names with just passing version through hiera ? ThanksSuresh Rajagopal -- You received this messag

Re: [Puppet Users] mysql package name

so they can be overridden by users, often via hiera. On Monday, August 29, 2016, Suresh Rajagopal wrote: Hi Peter, Yes passing package name works. But i have to pass package name for all the components. Something like below. I am just trying to figure out a way to handle this better. variable

Re: [Puppet Users] mysql package name

t; 'mysqld',          default       => 'mysqld'    } ThanksSuresh Rajagopal From: Peter Kristolaitis To: puppet-users@googlegroups.com Sent: Monday, August 29, 2016 11:03 AM Subject: Re: [Puppet Users] mysql package name There is a package_name parameter i

Re: [Puppet Users] mysql package name

e [0]. They solve it by having a package_ensure parameter to the mysql::server class which is one of [ 'present', 'latest, 'absent', 'x.y.z' ] where "x.y.z" is a version string.  [0] https://forge.puppet.com/puppetlabs/mysql#mysqlserver --Lowe Schmidt

[Puppet Users] mysql package name

Hi, Puppet 3.4 with hieara. what is the best place to define package name within a module? package name varies based on package version. Thanks Suresh Rajagopal -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from