rsion
2.6.x of the puppet client. It's just some machines had this older version
and I was hoping to get away with it so to speak.
Regards
Manoj
On Monday, June 24, 2013 1:34:27 PM UTC+1, R.I. Pienaar wrote:
>
>
>
> - Original Message -----
> > From: &qu
pet versions have a problem with this.
>
> - Keith
> On 24 Jun 2013 01:11, "Manoj Bhola" >
> wrote:
>
>> Hi,
>>
>> I hope someone can help.
>>
>> I have created a custom class module which updates a configuration file.
>>
>>
mailto => "supportadmin@localdomain",
> enable => "false",
> }
>
> The - might be confusing.
>
>
>
> On Sunday, June 23, 2013 10:34:31 AM UTC+10, Manoj Bhola wrote:
>>
>> Hi,
>>
>> I hope someone can help.
>>
&g
Hi,
I've created a custom class module and I can deploy it using the puppet -e
"include custom.pp" command and all works great.
But if I call the class via a manifest file, puppet throws an error.
manifest:
class { custom-class:
addr => '192.168.69.204',
enable => false,
ensure => stopp
Hi,
I hope someone can help.
I have created a custom class module which updates a configuration file.
When I use the puppet command: puppet -e "include custom", the file is
replaced using the template file included in the module correctly.
When I try to update settings in the configuration fil