I'd like to use the Catalog Preview tool as part of module spec tests, to
ensure that code in each module will work correctly in both versions of
Puppet?
Is it possible to use the Catalog Preview tool without a real Puppet Master
infrastructure?
Thanks,
RT
--
You received this message becau
On Friday, January 22, 2016 at 1:27:33 PM UTC-5, Hailee Kenney wrote:
>
> Facter 2.4.5 is a backwards-compatible bug-fix release in the Facter 2
> series.
>
> This release includes minor bug fixes to several different facts.
>
> To download Facter, follow the instructions here:
> http://docs.pupp
On Wednesday, September 18, 2013 3:15:18 PM UTC+3, Henrik Lindberg wrote:
> Here are the possible alterantives:
>
> arity 1: String key
> arity 1: Hash options
> arity 2: String key, String | Type type
> arity 2: String key, Hash options
> arity 3: String key, String | Type type, Object defau
, better:
lookup('namespace::some_hash', { type => 'Hash', default => {'my_key' =>
'my_value'} })
On Thursday, September 12, 2013 12:13:37 AM UTC+3, Henrik Lindberg wrote:
>
> Thank you for the feedback, very good comments.
>
> See more in
And yes, a 3rd positional argument for the default would be fantastic. (For
now...)
On Thursday, September 12, 2013 12:13:37 AM UTC+3, Henrik Lindberg wrote:
> Does adding a 3d argument to lookup for default cut it for you?
>
> Regards
> - henrik
>
>
>
--
You received this message because y
I am reading over the release notes for Puppet 3.3, and buried under "data
in modules" is a link to ARM-9.
There is a good chance that I don't "get it" - Puppet is moving pretty fast
these days and I am still trying to get caught up with all of the changes.
I have only read the latest Puppet c
On Nov 1, 10:45 pm, Nan Liu wrote:
> On Tue, Nov 1, 2011 at 12:50 PM, Rob Terhaar wrote:
> > Hi All,
>
> > Does anyone have a good git pre-commit hook that's compatible with
> > Puppet 2.7? The example pre-commit hook on the PuppetLabs wiki[1] no
> > longer works, because the puppet binary no l
One problem that we frequently run into while building and supporting
puppet infrastructures, is some cowboy developer who insists that he
needs Python 3.1, PHP6, SWiG 1.3.40, etc, and these packages are not
available in our Distro's stable package repository.
Have you ever tried to build a slotte
On Jan 22, 10:45 pm, Todd Zullinger wrote:
> robbyt wrote:
> > For some reason, I'm unable to manage cron resources on my CentOS5
> > server:
>
> > manifest:
>
> > cron { "test":
> > command => '/bin/true',
> >
Hi All,
For some reason, I'm unable to manage cron resources on my CentOS5
server:
manifest:
cron { "test":
command => '/bin/true',
user=> 'root',
hour => '1',
}
And when I try to run this via puppetmasterd:
info: Caching catalog for ny-dev84.domain.com
err: Could not pre
> > Hi All,
>
> > I'm successfully using Exported Resources and StoreConfigs on my
> > puppet system. I'm able to populate the hosts files on all of my
> > nodes, and that's pretty cool.
>
> > My problem is that i'm not quite clear how to query the information
> > stored in the Exported Resources
Hi All,
I'm successfully using Exported Resources and StoreConfigs on my
puppet system. I'm able to populate the hosts files on all of my
nodes, and that's pretty cool.
My problem is that i'm not quite clear how to query the information
stored in the Exported Resources database for other things.
Hello All!
I would like to automatically add a header to all files/templates that
puppet manages on my servers. Something like "#if you break, my puppet
will fix it!!"
Is this possible?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
13 matches
Mail list logo
