':
server => “$vpn_server"
}
}
}
This screams for a better separation, to me. Unless you only have 1 set of
servers & clients…
— Maybe use a class, with the parameters pulling in the detai
NOTE: of course, I just wrote this whole thing, and I think using a hiera
lookup in the parameter might be about the same. That's at the end of
this.I'd still like to know if it breaks scope or the renderer...
However, it might be an option for overriding params.pp settings, without
having
thing that's *very* likely
to happen, and honestly, very hard to catch.
I'd really like to automate this check, and add it to commit hooks & jenkins..
Matthew Barr
mb...@mbarr.net
c: (646) 727-0535
--
You received this message because you are subscribed to the Google Groups
&q
> As far as I am aware, resource defaults still affect the dynamic scope in
> which they are declared, just as they always have done. The guide to which
> you referred seems to say that, too. That means that the defaults you
> declare in class 'mongo' apply to all resources declared in that cl
le {
'/etc/init.d/mongod':
ensure => present,
mode=> 755,
owner => 'root',
group => 'root',
source => 'puppet:///modules/mongo/mongod',
require => Package['mongo20-10gen-server'];
}
}
I've been looking at the problem of jenkins plugins, and they seem to fit the
custom package provider model vs a set of exec scripts in a module.
It's possible to get a list of versioned plugins that are present, and tell the
system to install new ones, either from a source string, or a version
ing one :)
On Dec 31, 2012, at 1:40 PM, Matthew Barr wrote:
> I'm working with a forge module that specifies & installs a yum repo before
> it installs the packages, then goes about it's business.
> * package isn't part of a standard repo
>
> We operate
:(
I was really asking after the puppet side of dealing w/ a module that wants to
install it's own repo's, vs the below.
Anyone else have any thoughts from the original post?
On Dec 31, 2012, at 1:56 PM, Dan White wrote:
> Here's what I do on the systems I manage:
>
> I use Cobbler and Pupp
gpgcheck => "1",
mirrorlist => absent,
gpgkey =>
"http://localrepo/jenkins/jenkins-ci.org.key";, }
}
Option 2:
modify the module to make the repo optional.
- probably a parameter w/ a default of install.
Mat
On Thu, Jul 26, 2012 at 4:52 PM, jcbollinger wrote:
>
> That is what I'm inclined to think, Matthew's denial notwithstanding. It
> is at any rate exactly the behavior that would be expected if some other
> package were installed or updated that required newer versions of the
> packages in questio
a
comment on the default behavior in the type reference.
( I'm not as worried about the docs - there has to be some default, and latest
isn't a terrible one. )
Matthew Barr
Technical Architect
E: mb...@snap-interactive.com
AIM: matthewbarr1
c: (646) 727-0535
On Jul 26, 2012,
09:43 web01 puppet-agent[1021]:
(/Stage[main]/Php/Package[php-domxml]/ensure) change from absent to present
failed: Could not find package php-domxml
This was the only package message logged, and yet we ended up with newer
versions.
Matthew Barr
Technical Architect
E: mb...@snap-int
12 matches
Mail list logo
