On Thu, May 14, 2009 at 00:35, Mike Renfro <ren...@tntech.edu> wrote:
> I may be naive here, since I've never written my own types, but I'm
> wondering if a puppet definition for mysql_user would be better than
> writing a native puppet type. Something like:
>
> mysql_user { "u...@localhost": password_hash => "hashed password" }
>
> with:
>
> define mysql_user (
> $password_hash = "someknownhash"
> ) {
> exec { "create_$name":
> command => "mysql -e 'CREATE USER $name IDENTIFIED BY PASSWORD
> $password_hash'",
> require => [Package["mysql-server"], Package["mysql-client"]],
> }
> }
This was the first thing I looked at, actually. Unfortunately, dealing
with permissions and grants is complex enough that I couldn't find a
way to do it in pure puppet.
> The types I see on the documentation pages all appear to be written in
> straight Ruby, and don't rely on external programs to run.
Using external programs is fine, even easy, as long as they are
already present when puppet loads the provider. If you sneak around
behind its back, you have to manage everything carefully yourself,
which is what I'm struggling with.
--J
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
