"OTOH, for a new user who is just starting to try things out, having it
watch a single file (probably the environment directory) isn't going to be
obvious. How are they do know that after editing a manifest they also need
to go and touch a directory. So, while the directory watching could give a
me
On Mon, Apr 28, 2014 at 4:51 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> On Wed, 2014-04-23 at 03:19 +0200, Henrik Lindberg wrote:
> > On 2014-22-04 8:06, Thomas Hallgren wrote:
> > > Would a MANUAL strategy make sense? I.e. instead of rebooting the
> > > master, just tell it to c
On 28/04/14 16:45, R. Tyler Croy wrote:
> 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 in
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.
>
> T
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:
cla
On Wed, 2014-04-23 at 03:19 +0200, Henrik Lindberg wrote:
> On 2014-22-04 8:06, Thomas Hallgren wrote:
> > Would a MANUAL strategy make sense? I.e. instead of rebooting the
> > master, just tell it to clear the cache (perhaps per environment).
> >
> > - thomas
> >
> Circling back to this. Andy poin
