On 06/05/16 21:00, Vince Skahan wrote:
Is there a way to shut up the undefined variable warnings in PE2016.1 ?
This is https://tickets.puppetlabs.com/browse/PUP-1780
Which was released in Puppet 4.4.0, and is thus in all PE2016.1 versions.
The input to docs (in the ticket) says:
"All referen
On 06/05/16 15:46, christg76 wrote:
Hi, I'm fairly new to Puppet and have been given the project of
upgrading an existing Puppet 2.7 site (Puppetmaster with
Apache/Passenger, and MySQL for exported resources, with hundreds of
clients), possibly to Puppet 4.
Just wanted to ask around if anybody ha
Is there a way to shut up the undefined variable warnings in PE2016.1 ?
Here's a trivial example:
# puppet apply -t --noop -e 'notice("this should print just a 'x' =>
x${foo}")'
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading fac
On 05/06/2016 06:59 AM, Martin Alfke wrote:
> Hi Chris,
>
> On 06 May 2016, at 15:46, christg76 wrote:
>
>> Hi, I'm fairly new to Puppet and have been given the project of
>> upgrading an existing Puppet 2.7 site (Puppetmaster with
>> Apache/Passenger, and MySQL for exported resources, with hund
On 5/6/16 7:22 AM, Rob Nelson wrote:
I have not done this, but I suspect a stairstep upgrade of 2.7 -> 3.0 ->
3.8 w/future parser -> 4.latest would be the easiest. You *might* be
able to skip to 3.8, technically, but I suspect your code would blow up
in strange ways that would be less obvious tha
Hi ,
On 06 May 2016, at 17:29, Jeff wrote:
> I'm working on a puppet module that automatically places the entire catalog
> into zenoss (this is based on an outdated module that I found on github)
>
> By default, I want to place every server in zenoss.
>
> I have a base class which is include
I'm working on a puppet module that automatically places the entire catalog
into zenoss (this is based on an outdated module that I found on github)
By default, I want to place every server in zenoss.
I have a base class which is included in every node. I want to add 'include
zenoss::client' i
I have not done this, but I suspect a stairstep upgrade of 2.7 -> 3.0 ->
3.8 w/future parser -> 4.latest would be the easiest. You *might* be able
to skip to 3.8, technically, but I suspect your code would blow up in
strange ways that would be less obvious than the additional step.
Puppetconf 2015
Currently i'm using Vagrant and bash scripts to provision a local dev
environment. I'm working on moving this to Puppet and running into an issue
with creating a symlink to my apache document root that I cant seem to sort
out.
These are the commands in the bash script i'm trying replace/replica
Hi, I'm fairly new to Puppet and have been given the project of upgrading
an existing Puppet 2.7 site (Puppetmaster with Apache/Passenger, and MySQL
for exported resources, with hundreds of clients), possibly to Puppet 4.
Just wanted to ask around if anybody has got experience with such an
upgra
Hi Chris,
On 06 May 2016, at 15:46, christg76 wrote:
> Hi, I'm fairly new to Puppet and have been given the project of upgrading an
> existing Puppet 2.7 site (Puppetmaster with Apache/Passenger, and MySQL for
> exported resources, with hundreds of clients), possibly to Puppet 4.
“fairly new
On Friday, May 6, 2016 at 5:19:50 AM UTC-5, Alexander Dacre wrote:
>
> I'm looking to build my first module with custom types and providers, but
> I have some questions that I've been unable to find answers to.
>
> Lets say I have an application with a REST API that allows the creation of
> wid
I'm looking to build my first module with custom types and providers, but I
have some questions that I've been unable to find answers to.
Lets say I have an application with a REST API that allows the creation of
widgets. My custom type and provider would define what the widget looks
like and c
13 matches
Mail list logo
