On Friday, July 12, 2013 8:21:01 AM UTC-5, Markus Shorty Uckelmann wrote:
>
> Hi all,
>
> I want to do the following:
>
> package { 'zookeeper-deb':
> ensure => 'installed',
> name => 'zookeeper',
> }
> package { 'zookeeper-gem':
> ensure => 'installed',
> name => 'zookeeper',
> provider => 'gem',
> }
>
> This just fails with "Cannot alias Package[zookeeper-gem] to
> ["zookeeper"] [...] resource ["Package", "zookeeper"] already declared".
>
> Is there a nice way to not handle this with "realize" or defines? At
> least that is what I was able to dig up. Please correct me if I'm wrong.
>
No amount of defines, virtual resources, or other tricks, nice or
otherwise, will persuade Puppet to accept two resources of the same type
with the same name or title.
>
> I understand that from the Puppet point of view both are package
> resources with the same name. But from the human(my) side this doesn't
> make much sense.
>
>
Feel free to construe it as a shortcoming of Puppet. Personally, though, I
think it is unwise to create such a requirement for yourself in the first
place. It is unwise to use multiple package managers with overlapping
areas of authority. Instead, obtain or create packages for the host
system's native package manager (apparently Apt in this case).
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
