On Apr 8, 2009, at 3:58 AM, Graham Stratton wrote:
>
> I'm using puppet 0.24.7. I have the following simple setup:
>
>
> define buildout($path, $eggs, $python) {
> file { $path:
> ensure => directory,
> }
> file { "$path/bootstrap.py":
> source => "puppet:///pythonutils/bootstrap.py"
> }
> file { "$path/buildout.cfg":
> content => template("pythonutils/buildout.cfg"),
> }
> exec { "bootstrap_$path":
> require => [File["$path/bootstrap.py"], File["$path/
> buildout.cfg"]],
> command => "cd $path; python2.5 bootstrap.py",
> unless => "test -d $path/bin",
> }
> exec { "build_$path":
> require => Exec["bootstrap_$path"],
> command => "cd $path; ./bin/buildout",
> subscribe => File["$path/buildout.cfg"],
> refreshonly => true
> }
> }
>
> The bottom resource depends on the one above it. But if that one
> initially fails to run, then the bottom one will not be triggered when
> it eventually does. Is this expected behaviour when refreshonly is
> set?
Any resource subscribing to another resource should *always* run when
that subcribed-to resource changes something.
But there's got to be something else going on; Puppet doesn't maintain
state between runs, so either it fires off an event or it doesn't, and
if it does, then the other resource should get triggered.
--
It's a small world, but I wouldn't want to paint it.
-- Stephen Wright
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
