On 2011/02/16, at 09:20, jcbollinger wrote:
> In general, if Puppet attempts to apply resources in a sequence that
> doesn't work, then it means that there are resource relationships that
> are not implicit and have not been declared. That's exactly the case
> in the OP's manifest: there is nothing in it that would create an
> order relation between devices::device_node instances and the
> directories named in their $dir parameters. Exec resources are not
> documented to (and evidently do not) autorequire any part of the path
> to their 'cwd' or 'creates' parameters. The sequence of declarations
> in the manifest is irrelevant.
Actually, yes they are documented to do that. From the documentation for
'require'[1]:
Currently, exec resources will autorequire their CWD (if it is specified)
plus any fully qualified paths that appear in the command. For instance,
if you had an exec command that ran the myscript mentioned above, the
above code that pulls the file down would be automatically listed as a
requirement to the exec code, so that you would always be running againts
the most recent version.
And, as noted in my original post, I did try replacing the 'cwd' with a
'require', and tried moving the 'require' to the call to devices::device_node
rather than in its definition. Neither alternative worked.
--
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.
