On Aug 10, 2012, at 9:04 AM, jcbollinger <john.bollin...@stjude.org> wrote:
> > > On Thursday, August 9, 2012 7:24:23 AM UTC-5, pmbuko wrote: > Adding this parameter to your file resource, > > notify => Exec['Deploy Code'], > > and these parameters to your exec resource, > > require => File['/var/tmp/deploy.tar'], > refreshonly => true, > > will create the appropriate dependency. Basically, it makes sure the file > resource must run before the exec. Puppet manifests do not run in a top down > manner, do it's important to specify the order of resouces when necessary. > > Technically, either the 'notify' on one side or the 'require' on the other is > sufficient to create a relationship, and 'refreshonly' is a tangential issue. > I prefer to avoid specifying relationships redundantly, as it complicates > maintenance. The Exec's relationship to the File is a true dependency, so I > would express the relationship on that side. > > Inasmuch as it makes sense to deploy the code only when the tarball changes, > 'refreshonly' is a good choice. In that case, I would use: > > In the File: > # nothing special > > In the Exec: > refreshonly => true, > listen => File['/var/tmp/deploy.tar'] > > Note also that if you're going to use this means to deploy code then you > should probably put the tarball in a permanent location and plan on leaving > it there. If you delete it after the deployment then Puppet will copy it > back down (and trigger a new deployment) on its next run. > > > John The listen parameter is new to me. Good to know! -- Peter -- 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.
