As another option, I believe you can use:
file { "/etc/abc.conf":
ensure => present
content => "rundir= /central/$hostname/\nlogdir=
$hostname.log"
}
- Jeff
On 06/18/2010 01:49 PM, Nigel Kersten wrote:
On Fri, Jun 18, 2010 at 11:47 AM, CraftyTech
I'm having the same issue on CentOS5.2 with the following packages:
*yum*
puppet-0.25.5-1.el5
puppet-server-0.25.5-1.el5
rubygems-1.3.1-1.el5
ruby-shadow-1.4.1-7.el5
ruby-devel-1.8.6.111-1
ruby-1.8.6.111-1
ruby-ri-1.8.6.111-1
ruby-docs-1.8.5-5.el5_3.7
ruby-augeas-0.3.0-1.el5
ruby-irb-1.8.6.111-1
r
Hi all
We've created a little module to help people interested in developing,
testing or working on the Puppet source:
http://forge.puppetlabs.com/puppetlabs/DeveloperBootstrap
This module installs everything someone needs on Red Hat, Fedora,
CentOS, Debian, Ubuntu or Solaris in order to develop
Yeah, that looks better. Thanks.
On Jun 18, 2:49 pm, Nigel Kersten wrote:
> On Fri, Jun 18, 2010 at 11:47 AM, CraftyTech wrote:
> > Hello All,
>
> > I have quick question for you; How can I pass a variable to a
> > static file that I'm distributing via puppet? i.g, :
> > class abc {
> >
On Fri, Jun 18, 2010 at 11:47 AM, CraftyTech wrote:
> Hello All,
>
> I have quick question for you; How can I pass a variable to a
> static file that I'm distributing via puppet? i.g, :
> class abc {
> file { "/etc/abc.conf":
> ensure => present
> source => "puppet://
Hello All,
I have quick question for you; How can I pass a variable to a
static file that I'm distributing via puppet? i.g, :
class abc {
file { "/etc/abc.conf":
ensure => present
source => "puppet:///sys/abc.conf}
}
puppet:///sys/abc.conf contains
Is it possible to express node inheritance when using external nodes. If it
is could someone post what the yaml might look like?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
On 06/18/2010 02:18 PM, Nigel Kersten wrote:
On Fri, Jun 18, 2010 at 10:34 AM, Robert Scheer wrote:
To facilitate developing, testing and releasing puppet code, we use
different environments. That works very well. The only problem is that
I cannot prevent puppet from mailing a report, nor d
On Fri, Jun 18, 2010 at 10:34 AM, Robert Scheer wrote:
> To facilitate developing, testing and releasing puppet code, we use
> different environments. That works very well. The only problem is that
> I cannot prevent puppet from mailing a report, nor direct it somewhere
> else, when using a differ
Hi all!
How i may use in legacy puppet (0.24.[89]) custom facts in functions?
In new documentation not good faq about this:
http://docs.reductivelabs.com/guides/plugins_in_modules.html this
documentation has information about new versions (25.5) and very old
(prior 0.24.4),
not about our 0.24.8 >
To facilitate developing, testing and releasing puppet code, we use
different environments. That works very well. The only problem is that
I cannot prevent puppet from mailing a report, nor direct it somewhere
else, when using a different environment.
The file /etc/puppet/puppet.conf on the puppet
To follow up, I had absolutely been looking at the problem for too long.
The filenames were snmpd.conf and snmpd.options, so I was just missing the
d.
-Aaron
On Thu, Jun 17, 2010 at 4:44 PM, Aaron Blew wrote:
> I'm getting the following errors in the module I'm writing to maintain my
> snmpd
- "Silviu Paragina" wrote:
> >
> I've been left with the impression that if augeas fails for provider
> reasons it fails the whole run.
>
> My test case would imply the same thing.
>
> sil...@puppet-test:/etc/puppet/repo/development/modules/puppet$ cat
> test.pp
> augeas
> { "puppet sett
On Wed, Jun 16, 2010 at 21:27 +0300, Silviu Paragina wrote:
> So are there any better ideeas?
Not a better idea, just another idea:
We simply repackaged facter with lsb-release as extra dependency. As we
already have our own package repository to install software released by
our developers, this
On 17.06.2010 14:30, David Schmitt wrote:
On 6/17/2010 1:02 PM, Silviu Paragina wrote:
On 17.06.2010 10:53, David Schmitt wrote:
On 6/16/2010 8:27 PM, Silviu Paragina wrote:
This is somewhat related to an older thread. The topic was how to
install some perquisite packages for puppet, like auge
Darn it. now I see the typo. I looked at your comment for 5 mins before i
noticed. Oh well :) Thanks alot!
On 17 June 2010 19:55, Gabriel Filion wrote:
> On 2010-06-17 06:31, Tore wrote:
> > I'm troubled with a node-definition not able to resolve a class:
> > Could not find class rhnsd::common
It looks like it's working now This is what I get when I click
on yaml ...
---
parameters:
puppetmaster: puppet
classes: []
environment: ""
It doesn't let me edit it thought... It seems to be static..
On Jun 17, 9:54 pm, Ohad Levy wrote:
> that is not a limitation, and usually actually w
Thanks Patrick!
I like the separation of the values being set and adding the comments. That
makes complete sense.
As for the over-writing of the values, you were absolutely right. The
main.cf was being managed by a different class that another Ops engineer had
implemented and I was unaware of.
Hi,
IMHO the best way will be to develop a small fact that indicates whether
it's a prod or non-prod environment and use it in the ressource to select
the right password :
user {"my-user":
ensure => present,
password => $yourfact ? {
'prod' => 'production-password',
'non-prod' => 'non
19 matches
Mail list logo
