On Wed, Feb 19, 2014 at 1:58 PM, Wolf Noble <loi...@wolfspaw.com> wrote:
>
>
> One thing I've seen done is something like the following contrived example:
>
> class core{
> @package { 'build essential':
> ensure => 'installed',
> tag => 'core_packages'
> }
> Package <| tag == 'core_packages' |>
> }
>
> From my probably incomplete understanding, virtualizing and realizing the
> packages like this allows for multiple classes to declare the resource, and
> as long as the ensure value is the same across declarations, the
> declarations can cohaibtate in the same catalog.
>
> Am I missing something that would make this an antipattern as well?
> (entirely possible)
>
You still can't declare two virtual package, only the ability to realize as
many times as necessary. This requires module authors to agree on the same
set of virtual resource module. I think people just want to say
ensure_package('buildessential')
Instead of worry about which module on forge has this virtual resource and
whether it's the same as another author's choice of virtual package module.
If the compiler can recognize the same package and avoid the need for a
special function, even better.
Nan
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/CACqVBqB9-JBA1eB09owoxXEX5vSPoYoJaBVd_4-E-TXjsn1d6g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
