In my previous thread "Can I make my entire module "depend" on rubygems being installed?" I think I mischaracterized the problem.
Basically, I would like to use a Ruby gem inside of a Puppet module which
contains a custom provider. There's an inherent problem in this appraoch, for
example:
class {
'jenkins' :
require => Package[mygem];
}
This iwll require *two* Puppet runs to operate correctly, one to install the
gem properly, and the second to load the gem properly into the Puppet runtime
environment.
The best solution I have to prevent this 2-run problem is to vendor my ruby gem
into the Puppet module and hope that I can keep track of upstream properly for
necessary bug fixes and security patches :(
Is there no better way to depend on shared Ruby code for my module? Does the
Modulefile allow for declaring a dependency like this to be installed at
`puppet module install` time?
Cheers
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------
pgpoCoEgv0IPb.pgp
Description: PGP signature
