HI all,

First thing - I've been keeping the puppet manifest, configs,
functions etc. in svn, but due to a few dodgy checkouts to the
puppetmaster (non production) i'd like to get a better process in
place.  Are people using anything to test the puppet deployments?
preferably in a continuous environment.  How are you
deploying/releasing puppet manifests etc.. to the master?

Also a quick puppet question:

I use this function to get an application tar file which is specified
in node manifest $dist = app-37434-3439493-.tar.gz:

 exec { "get-app":
                cwd     => "/opt/dist",
                creates => "/opt/dist/$dist",
                path    => ["/usr/bin", "/usr/sbin"],
                command => "curl -s -f -o $dist http://$repoUrl/app/$dist";,
                before  => Exec["untar-dist"],
        }

The 'creates' value ensures that it doesn't get re-downloaded on every
puppet poll.  Any new value to $dist works fine, but if $dist becomes
an old value then the file already exists, so the exec and subsequent
calls are not run.

I guess using the file type would cure this, but I don't want the
master to serve the file, as I use a similar curl command to get the
file from S3 if specified.

Thanks,

Matt

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to