On 04/28/2014 05:45 PM, R. Tyler Croy wrote:
> 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 :(
I vaguely remember talk of providers coming available during the agent
run. Perhaps this is what you're looking for here. If so, it would
probably Just Work.
> 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?
I believe this question is not valid. The gem is required agent side,
yes? puppet module install will operate master side, where gem support
should be of no relevance.
Regards,
Felix
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/535E78DD.7040603%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/d/optout.
