On Friday, October 9, 2015 at 2:53:47 PM UTC-5, Costya Regev wrote:
>
> Hi ,
> I have a question regarding managing puppet virtual Resource i have this
> code:
> class Carb::chocolatey {
> include chocolatey
> # [Make Chocolately default package provider]
> Package { provider => chocolatey }
>
> $packages = [ '7zip', 'dotnet4.5']
> ensure_packages($packages)
> }
> my problem is that i have this resource declared in my base module and
> whenever i try to apply this manifest on a node that has the base module i
> get a "Duplicate Decleration" , is there a way to ensure i will install
> both packages without changing my base module .
>
We really don't have enough information to answer the question confidently,
but I'm inclined to say it's unlikely that you can do anything to the class
you presented that will avoid needing to modify other classes needing to
modify other classes to fix your duplicate declaration issue. In
particular, your title suggests you're thinking along the lines of virtual
resources, but that would not be a fruitful direction (in the sense of
avoiding changes elsewhere). You're already using ensure_packages() ,
which is about the most you can do unilaterally. It also is *always* an
inferior solution when it solves the problem at all.
> I know that when im using include class_name for example i can declare it
> more than twice and i will not get an Error for duplicate Decleration , is
> there a way to apply this on packages ?
>
>
Each resource -- as distinguished by type and title, and also by type and
name -- can be declared at most once in the process of building a given
catalog, regardless of whether the resource so declared is concrete,
virtual, exported, or imported. Classes are not resources, and you can
declare them more than once via include-like declarations, but if you treat
them as if they were resources (by using resource-like class declarations)
then you indeed can get duplicate declaration issues.
The best solution is to choose for each resource one class whose
responsibility it is to declare that resource, and for all other classes
that require the resource to be declared to use an include-like class
declaration to ensure that class is assigned to the target node. I'm not
suggesting a separate class for every resource, nor even that it is a good
idea to organize classes around which resources they declare. If you want
advice on organizing your local site's classes, however, then in two+ years
I have not found a better general pattern than Craig Dunn's "Roles &
Profiles".
John
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/471fd0eb-2acb-412f-a31c-902f6c7eb9e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
