On 23.08.2012, at 14:25, Axel Bock wrote:
> Ah maybe I'm too stupid but the whole puppet dependency resolution
> _seriously_ annoys me, so this is half a rant post, half a plea for someone
> to enlighten me about this dependency thing puppet has going.
>
> I have another custom define which basically contains an exe and a file
> (directory). The file is not dependent on anything, but everywhere I use it I
> add a "require" to the define roughly like this:
> my_rsync_define { ... require => something_else_before }.
>
> unfortunately puppet simply does not care and tries do create the directory
> as the first step in the process, failing. this is not intuitive _at all_.
> the dot graph (I used graphviz a lot today) tells me that the DEFINE itself
> actually IS dependant on the something_else_before I added, but the DIRECTORY
> WITHIN THE DEFINE ... stands alone. I personally think this is ... not great.
> but maybe it's because I have an old version. File autorequires don't seem to
> work too well here, too, I think.
>From my experience:
best is to add ordering to all resources.
- inside a define
- inside a class
- between classes
>
>
>
>
>
>
> Am Mittwoch, 22. August 2012 14:27:03 UTC+2 schrieb Axel Bock:
> Hi readers
>
> another question for my little puppet project: Can I (and if yes, how) define
> dependendies between puppet "defines"? (define like in define
> mymodule::mydefine() {...})
>
> Example: I have a define "prepare_cool_thing" and another define
> "cool_thing". Both can be on a machine several times (quite, actually, like
> vhosts :). So this is entirely valid:
>
> prepare_cool_thing{ "name1" : }
> cool_thing{ "name1" : }
>
> prepare_cool_thing{ "name2" : }
> cool_thing{ "name2" : }
>
> I'm sure you get it. BUT. I'd like to state within the cool_thing define that
> the prepare_cool_thing was executed. Can I do that? The following does not
> seem to do what I want:
>
> Prepare_cool_thing[ "name1" ] -> Cool_thing[ "name1" ] # naah, does not work.
>
>
> Thanks & greetings!
> Axel.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/9BNRHcD0VSoJ.
> 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.
--
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.
