There's no way to have the defaults in the top scope if you put them in a
module. Module implies class, which implies a scope under top scope.
Site.pp would be the appropriate place, but keep in mind there is no way to
"enforce" these defaults.
There's a fairly common practice these days of setting resource defaults in
a class when you have multiple resources with the same parameters. I
believe setting any defaults at a lower scope will cause puppet to ignore
the ones set at the higher scope (not to merge them), so it's likely
there's not a good solution to what you're trying to do short of a commit
hook that denies any defaults outside site.pp.
On Monday, March 18, 2013 6:01:10 AM UTC-6, david...@gmail.com wrote:
>
> hi,
>
> Specifically I would like to have something like top scope resource
> defaults so as to enforce,... well,... default behaviors across our modules
>
> for example, with the exec type: Exec { logoutput => on_failure }
>
> However our puppet code base is rather extensive and the responsibility
> for it is "distributed", so I was wondering if there was a way to set those
> up in one place and affect all class and type instances across our
> deployments.
>
> The only way I can think I can think of would be to declare it at the top
> level of the site.pp but I would rather have in a module (we have base
> modules which get installed on every nodes)
>
> is there any other option?
>
> thanks you,
> david.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
