Wait, what?
You're starship-overriding the one header resource to use whatever
target "gets lucky"? I think this is bound to break, no?
So basically you want all generated files to use the same header
template? Hmm.
I believe what you want is another defined type that represents "the
header snippet for a specific pam config file" and declares a
concat::fragment "$name-header" or somesuch. Each of the other defined
types then contains an instance of this new type, probably not passing
more than the name.
This is not a use case for virtual resources as far as I can tell.
Cheers,
Felix
On 02/12/2013 03:21 PM, Darin Perusich wrote:
> Concat::Fragment <| title == 'header' |> { target => $limits_conf,
> name => "limits" }
--
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.
