On Thursday, 8 September 2016 07:54:07 UTC-4, amateo wrote:
>
>
> So I'm thinking the possibility to create my own types extending
> them.
> Is there any documentation about extending types. All documentation I
> have found is about creating a completely new type, but I haven't found
On Wednesday, 7 September 2016 19:11:04 UTC-4, Henrik Lindberg wrote:
>
>
> The call to `find` is in Ruby, not in puppet. There are numerous calls
> to find in the Ruby code base.
>
Yeah, all the stuff I was looking at was ruby. It hadn't occurred to me to
check the puppet codebase itself
Having just installed zleslie/pkgng in order to ma nage repositories on my
FreeBSD hosts (which in turn required and installed puppetlabs/stdlib), I'm
now getting the following error from my puppet runs:
% sudo puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving
On Tuesday, 9 August 2016 06:12:33 UTC-7, jcbollinger wrote:
>
>
>
> Some people do hack together means to do the job more or less as you
> initially envisioned, but don't confuse mechanism with result. I would not
> be surprised if you had seen examples of exactly what I describe, without
>
On Monday, 8 August 2016 14:02:39 UTC-7, Christopher Wood wrote:
>
> On Mon, Aug 08, 2016 at 11:28:55AM -0700, Matthew Pounsett wrote:
> >I'm using puppet 4.4.1. I have a case where I need the IP addresses
> of
> >all the servers that fit a certain set
I'm using puppet 4.4.1. I have a case where I need the IP addresses of all
the servers that fit a certain set of criteria to appear in a YAML list in
a config file on a particular host.
It seems like the first step would be to create an exported resource with
the required data in it, but I
On Monday, 11 July 2016 10:31:45 UTC-4, R.I. Pienaar wrote:
>
>
> best avoid create_resources in puppet 4 :)
>
Why is that?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it,
On Friday, 8 July 2016 04:27:26 UTC-4, Peter Faller wrote:
>
> Are you using the create_resources function to instantiate the resources?
> It takes a third argument containing default values:
>
> $widgets = hiera('widgets', {})
> $widget_defaults = hiera('widget_defaults', {})
>
I have a defined resource type (let's call it `widget`) which gets defined
multiple times per customer. Each customer has their own default
configuration values for their widgets, and these are very rarely (but
occasionally) overridden. I'd like to minimize the amount of typing
necessary
I have a defined resource type (let's call it `widget`) which can be
defined multiple times per customer. Each customer has different default
values for their set of widgets which are rarely overridden, and I'd like
to minimize the typing necessary when someone adds a new widget to a
On Tuesday, May 3, 2016 at 10:02:30 AM UTC-4, Lindsey Smith wrote:
>
>
>
> On Mon, May 2, 2016 at 1:54 PM, Matthew Pounsett <matthew@rightside.co
> > wrote:
>
>>
>> I'm setting up a test deployment of the latest PE. I haven't run PE for
>>
I'm setting up a test deployment of the latest PE. I haven't run PE for a
couple of years, and it looks like a few (perhaps a lot of) things have
changed.
I have a completely fresh install of puppet-enterprise-2016.1.1-el-7-x86_64
on Centos 7. I've added a module as
On 10 September 2014 07:30, Daniel Siechniewicz dan...@siechniewicz.com
wrote:
Hi,
Sounds like a job for https://github.com/dalen/puppet-puppetdbquery
potentially? pdbresourcequery or maybe even the hiera backend.
Hiera doesn't apply here, because it's data gathered from the servers
(mostly
On 10 September 2014 08:08, Daniel Siechniewicz dan...@siechniewicz.com
wrote:
Hi,
This particular hiera backend, from what I understand, is extracting
values from puppetdb on the fly, so you don't have to put any values
in hiera yaml/json files save for a relevant puppetdb query. This
On 10 September 2014 12:57, José Luis Ledesma joseluis.lede...@gmail.com
wrote:
Perhaps you can use datacat_fragments exported resources and then collect
them and put them together with the datacat_collector.
https://github.com/richardc/puppet-datacat/
That looks really promising. It'll
On Tuesday, 29 January 2013 00:29:43 UTC-5, Keith Burdis wrote:
You can set the default values to undef and then the standard user type
will use its defaults (if any). It usually makes sense to default the
ensure parameter to 'present' though because if it is undef then nothing
will
On Tuesday, 29 January 2013 02:05:30 UTC-5, yarlagadda ramya wrote:
Hi all,
I have written the following code...
$someendpoint1=12345
$someendpoint2=54321
$prop = /app/tcs/temp.properties
file{'temp.properties':
path =$prop,
ensure ='present',
content
On Tuesday, 29 January 2013 04:34:56 UTC-5, jim wrote:
The easiest option would be to add different manifests for different
groups / teams within site.pp, but if I make changes to the sub-manifests,
i'd need to touch the site.pp file for changes to kick in, which could
also effect the
On Tuesday, 29 January 2013 10:07:29 UTC-5, Ti Leggett wrote:
I'm not sure I fully agree with this from a design standpoint. In
object-oriented programming, one of the design principles is that variables
relating to the object are encapsulated within the object and exposed or
not
On Tuesday, 29 January 2013 13:58:20 UTC-5, Ti Leggett wrote:
I include that in the module that installs the shell packages and
configures them, in my case, I call it base. In other words, the variables
should be as close to the things they affect or are affected by. Just
because every
On Monday, 28 January 2013 11:14:59 UTC-5, jcbollinger wrote:
define site::user (
$comment,
$ensure,
$home,
$name = $title,
Don't do that ($name = $title). Puppet provides it automatically (both
the parameter and the default).
In this case, $name
I'm trying to extend the standard 'user' type to add maintenance of some of
the contents of a user's home directory, and I'm trying to avoid creating
an entirely new custom type if I can. The approach I'm taking is to create
a site::user defined type which in turns calls the standard user
On 2011/02/16, at 07:11, randomcontrol wrote:
I removed the facts directory and puppet now starts without
problems, but it doesn't create a facts-file or -directory
automatically.
I reached the same conclusion. I still have no idea why the complaint or even
really what generated it.. in
On 2011/02/16, at 03:44, Felix Frank wrote:
Hi,
here's what I'd do:
Devices::Device_node {
dir = $homedir/${service_num}/dev/,
require = File[$homedir/${service_num}/dev/],
}
I tried that as well (noted in the original post). That's
On 2011/02/16, at 09:20, jcbollinger wrote:
In general, if Puppet attempts to apply resources in a sequence that
doesn't work, then it means that there are resource relationships that
are not implicit and have not been declared. That's exactly the case
in the OP's manifest: there is nothing
On 2011/02/16, at 10:56, Felix Frank wrote:
Adding an appropriate requires = to Devices::device_node
instantiations, as suggested, should do the trick. Alternatively, the
requires = could be put on one of the resources inside the defined
type (in this case, the only candidate is the Exec).
On 2011/02/16, at 12:53, Matthew Pounsett wrote:
Actually, yes they are documented to do that. From the documentation for
'require'[1]:
Hrm.. I meant to include the URL there:
http://docs.puppetlabs.com/references/stable/metaparameter.html
I'll also note that I'm not too surprised you
On 2011/02/14, at 12:21, Daniel Pittman wrote:
Hey.
I think this discussion totally deserves a feature/bug report in redmine,
because both positions are reasonable. They do point to a hole where our
specifation seems vague, and where we *should* have made a decision: right
now we have
On 2011/02/14, at 11:12, Felix Frank wrote:
On 02/10/2011 08:47 PM, Matthew Pounsett wrote:
The docs are vague on how the two interact.. but it seems to me that
'creates' will override 'onlyif' in an exec clause. i.e. if the file named
by 'creates' exists, then 'onlyif' is ignored
I'm having an issue solving dependencies inside defines, where the paths to
various resources are variable. It seems like puppet isn't expanding all of
the variables when it constructs the catalog, so it's unable to find the
resources necessary to build things in the right order.
I've
A few days ago another user posted an issue with complex hashes[1]; it looks
like a parser bug, and a bug report was opened[2]. I seem to be having a
similar problem, but I haven't been able to make the same workaround function.
This is the data structure I'd like to be using, but puppet
The docs are vague on how the two interact.. but it seems to me that 'creates'
will override 'onlyif' in an exec clause. i.e. if the file named by 'creates'
exists, then 'onlyif' is ignored. Is someone able to confirm that?
Thanks!
--
You received this message because you are subscribed to
On 2011/02/09, at 15:32, DigitalWonk wrote:
Hello puppet world,
I'm sure this is probably an easy fix, but I cannot seem to resolve this
issue. The puppetmaster starts correctly and so does the puppet agent, which
receives the update correctly if I restart the puppet agent service
I'm having an issue with the default puppet.conf distributed with puppet 2.6.4
(FreeBSD port). I've reproduced the problem with a completely fresh install on
a completely fresh OS in a VM. Under these conditions, running puppetmaster
with no config is fine, but simply moving the
34 matches
Mail list logo
