Re: [Puppet Users] suppressing undefined variable warnings in PE2016.1
This is a hiera design i inherited -- each node can define a 'contextN' (1
through 6) in a contexts parameter in its hosts/${fqdn}.yaml, which is then
in the tree like:
contexts/.yaml
then the site.pp pulls in the 'contexts', sets $context1-6 and hiera uses
them as part of the lookup tree:
contexts/${context1}.yaml
contexts/${context2}.yaml
...
The initial lookup call to retrieve the contexts variable generates the
undefined warning. (since they aren't set yet)
-Ben
On Wednesday, February 15, 2017 at 7:40:22 PM UTC-8, Rob Nelson wrote:
>
> I believe that your hiera lookups won't be a problem. This is looking for
> the usage of previously undefined variables more than the content of the
> variables. If, however, it is truly undefined at that point due to some
> ordering error, it seems like you'd want it to flag instead of be
> nil/undef/etc.
>
> On Wed, Feb 15, 2017 at 10:19 PM Ben Hines >
> wrote:
>
>> I would be really cool if warnings could be disabled (And re enabled)
>> from code, like like pragmas in C++. That would let me keep the undefined
>> variables warning where it's needed, but ignore for other areas. (like
>> third party modules i may not care about)
>>
>> In my case, i am using hiera lookup paths that use variables that aren't
>> defined until later. (because they come out of hiera itself) The lookup
>> call that gets them warns that they are undefined, until later when i pull
>> them in. Perhaps that could be fixed on the lookup side, alternatively.
>>
>> -Ben
>>
>> On Friday, May 6, 2016 at 6:55:22 PM UTC-7, Henrik Lindberg wrote:
>>>
>>> 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 references to non existing variables will now generate a warning.
>>> Earlier puppet only warned about non existing qualified variables with
>>> more than one namespace segment.
>>>
>>> It is possible to disable these warnings by adding 'undefined_variables'
>>> to the setting 'disabled_warnings'.
>>>
>>> Note that in most cases there is no file/line information available, and
>>> this was one reason why only some cases were reported earlier. We expect
>>> to correct this in the next major version as it requires API breaking
>>> changes."
>>>
>>> Thus - you can get rid of those warnings by disabling that particular
>>> warning.
>>>
>>> Hope that helps
>>>
>>> Best,
>>> - henrik
>>>
>>> > 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 facts
>>> > Info: Loading facts
>>> > Info: Loading facts
>>> > Info: Loading facts
>>> > Info: Loading facts
>>> > Info: Loading facts
>>> > Info: Loading facts
>>> > Warning: Undefined variable 'foo';
>>> >(file & line not available)
>>> > Notice: Scope(Class[main]): this should print just a x => x
>>> > Notice: Compiled catalog for myhostname.com in environment production
>>> in
>>> > 0.04 seconds
>>> >
>>> > I see there is a --strict-variables where I can make compilation fail.
>>> > It seems that throwing the warning is the current default
>>> > I'm looking for a "yes I have a good reason so please just quit
>>> whining
>>> > about what I am doing" switch :-)
>>> >
>>> > Alternately, is there a way to check for the fact being not defined ?
>>> > I can not find any syntax that works in the 2016.1 parser.
>>> >
>>> > something along the lines of notionally the following:
>>> > if $whatever is defined print out 'whatever = $whatever'
>>> > if $whatever is not defined print out 'whatever is not defined' or
>>> null
>>> > or undef or whatever it evaluates to currently.
>>> >
>>> > I'm probably in interpreted language overload among perl/python/bash
>>> and
>>> > the Puppet DSL is just not grokking.
>>> >
>>> > --
>>> > 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, send
>>> > an email to puppet-users...@googlegroups.com
>>> > .
>>> > To view this discussion on the web visit
>>> >
>>> https://groups.google.com/d/msgid/puppet-users/dcfb928f-6e74-4974-9505-88d446c682f9%40googlegroups.com
>>>
>>> > <
>>> https://groups.google.com/d/msgid/puppet-users/dcfb928f-6e74-4974-9505-88d446c682f9%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>>
>>>
>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
>>>
>>> Visit my Blog "Puppet on the Edge"
>>> http://puppet-on-the-
Re: [Puppet Users] suppressing undefined variable warnings in PE2016.1
I believe that your hiera lookups won't be a problem. This is looking for
the usage of previously undefined variables more than the content of the
variables. If, however, it is truly undefined at that point due to some
ordering error, it seems like you'd want it to flag instead of be
nil/undef/etc.
On Wed, Feb 15, 2017 at 10:19 PM Ben Hines wrote:
> I would be really cool if warnings could be disabled (And re enabled) from
> code, like like pragmas in C++. That would let me keep the undefined
> variables warning where it's needed, but ignore for other areas. (like
> third party modules i may not care about)
>
> In my case, i am using hiera lookup paths that use variables that aren't
> defined until later. (because they come out of hiera itself) The lookup
> call that gets them warns that they are undefined, until later when i pull
> them in. Perhaps that could be fixed on the lookup side, alternatively.
>
> -Ben
>
> On Friday, May 6, 2016 at 6:55:22 PM UTC-7, Henrik Lindberg wrote:
>
> 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 references to non existing variables will now generate a warning.
> Earlier puppet only warned about non existing qualified variables with
> more than one namespace segment.
>
> It is possible to disable these warnings by adding 'undefined_variables'
> to the setting 'disabled_warnings'.
>
> Note that in most cases there is no file/line information available, and
> this was one reason why only some cases were reported earlier. We expect
> to correct this in the next major version as it requires API breaking
> changes."
>
> Thus - you can get rid of those warnings by disabling that particular
> warning.
>
> Hope that helps
>
> Best,
> - henrik
>
> > 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 facts
> > Info: Loading facts
> > Info: Loading facts
> > Info: Loading facts
> > Info: Loading facts
> > Info: Loading facts
> > Info: Loading facts
> > Warning: Undefined variable 'foo';
> >(file & line not available)
> > Notice: Scope(Class[main]): this should print just a x => x
> > Notice: Compiled catalog for myhostname.com in environment production
> in
> > 0.04 seconds
> >
> > I see there is a --strict-variables where I can make compilation fail.
> > It seems that throwing the warning is the current default
> > I'm looking for a "yes I have a good reason so please just quit whining
> > about what I am doing" switch :-)
> >
> > Alternately, is there a way to check for the fact being not defined ?
> > I can not find any syntax that works in the 2016.1 parser.
> >
> > something along the lines of notionally the following:
> > if $whatever is defined print out 'whatever = $whatever'
> > if $whatever is not defined print out 'whatever is not defined' or null
> > or undef or whatever it evaluates to currently.
> >
> > I'm probably in interpreted language overload among perl/python/bash and
> > the Puppet DSL is just not grokking.
> >
> > --
> > 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, send
> > an email to puppet-users...@googlegroups.com
> > .
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/puppet-users/dcfb928f-6e74-4974-9505-88d446c682f9%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/puppet-users/dcfb928f-6e74-4974-9505-88d446c682f9%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
> --
> 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, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/aedd4f90-c872-4e1a-8144-b6603b9a3cc6%40googlegroups.com
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Rob Nelson
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion
Re: [Puppet Users] suppressing undefined variable warnings in PE2016.1
I would be really cool if warnings could be disabled (And re enabled) from
code, like like pragmas in C++. That would let me keep the undefined
variables warning where it's needed, but ignore for other areas. (like
third party modules i may not care about)
In my case, i am using hiera lookup paths that use variables that aren't
defined until later. (because they come out of hiera itself) The lookup
call that gets them warns that they are undefined, until later when i pull
them in. Perhaps that could be fixed on the lookup side, alternatively.
-Ben
On Friday, May 6, 2016 at 6:55:22 PM UTC-7, Henrik Lindberg wrote:
>
> 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 references to non existing variables will now generate a warning.
> Earlier puppet only warned about non existing qualified variables with
> more than one namespace segment.
>
> It is possible to disable these warnings by adding 'undefined_variables'
> to the setting 'disabled_warnings'.
>
> Note that in most cases there is no file/line information available, and
> this was one reason why only some cases were reported earlier. We expect
> to correct this in the next major version as it requires API breaking
> changes."
>
> Thus - you can get rid of those warnings by disabling that particular
> warning.
>
> Hope that helps
>
> Best,
> - henrik
>
> > 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 facts
> > Info: Loading facts
> > Info: Loading facts
> > Info: Loading facts
> > Info: Loading facts
> > Info: Loading facts
> > Info: Loading facts
> > Warning: Undefined variable 'foo';
> >(file & line not available)
> > Notice: Scope(Class[main]): this should print just a x => x
> > Notice: Compiled catalog for myhostname.com in environment production
> in
> > 0.04 seconds
> >
> > I see there is a --strict-variables where I can make compilation fail.
> > It seems that throwing the warning is the current default
> > I'm looking for a "yes I have a good reason so please just quit whining
> > about what I am doing" switch :-)
> >
> > Alternately, is there a way to check for the fact being not defined ?
> > I can not find any syntax that works in the 2016.1 parser.
> >
> > something along the lines of notionally the following:
> > if $whatever is defined print out 'whatever = $whatever'
> > if $whatever is not defined print out 'whatever is not defined' or null
> > or undef or whatever it evaluates to currently.
> >
> > I'm probably in interpreted language overload among perl/python/bash and
> > the Puppet DSL is just not grokking.
> >
> > --
> > 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, send
> > an email to puppet-users...@googlegroups.com
> > .
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/puppet-users/dcfb928f-6e74-4974-9505-88d446c682f9%40googlegroups.com
>
> > <
> https://groups.google.com/d/msgid/puppet-users/dcfb928f-6e74-4974-9505-88d446c682f9%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
>
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/aedd4f90-c872-4e1a-8144-b6603b9a3cc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: hiera deep hash merges broken
On 02/15/2017 09:24 PM, Eric Sorenson wrote: > That's great to hear François, thank you for testing the patch! You are welcome. :) > Our plan at > this point is to accumulate a couple more fixes and ship a new build by > Tuesday 21 Feb - > > I don't want to generate a new build containing only the fix in PUP-7215 > because > (a) there is QA work underway on the current release that may turn up new > things that need fixing by the end of the week > (b) there is a simple workaround in PUP-7216 which is that you can > s/hiera_hash/lookup/ as the function that you call. Ok, no problem, it's better to hold your workflow. Bye. François Lafont -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/442a6d8a-387b-1dbc-031b-4605842b706f%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: puppet open source reports and inventory to Satellite 6?
Hi Ryan, Thank you for sharing this very useful info. Did you ever try sending reports successfully from a standalone PuppetMaster server to a Capsule which in turn was relayed back to the Satellite? Regards, Suhail. On Friday, 4 November 2016 20:42:56 UTC, Ryan Anderson wrote: > > One more update. > > By default, all your puppet masters will dutifully forward reports of > *all* agents--RHEL or otherwise--and Satellite will dutifully receive and > display them. In my case, I had AIX and Solaris systems showing up in > Satellite I did not care for. Puppet reports do not contain facts, so to > filter out non-RHEL I had to filter out based on hostname. I added the line > in foreman.rb on my masters below that starts with 'break' to exit if the > hostname doesn't match. > > def process > > begin > > break if self.host !~ /.*linuxsrv.*|.*linuxws.*/ > > > See Puppet Labs documentation: > https://docs.puppet.com/puppet/latest/reference/reporting_write_processors.html > > > -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5299897d-8079-437c-8aff-ef847bb451a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] inline classes
Hello folks,
I'm wondering if it is possible to define-declare a class. Something like
inlining:
instead of:
```
include hello_distro
class hello_distro {
notify { "Running on distro: ${facts['os']['family']}": }
}
```
have something like:
```
include class hello_distro {
...
}
Thanks
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/421553c8-3881-44e9-9e8b-880917ac4b65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: hiera deep hash merges broken
That's great to hear François, thank you for testing the patch! Our plan at this point is to accumulate a couple more fixes and ship a new build by Tuesday 21 Feb - I don't want to generate a new build containing only the fix in PUP-7215 because (a) there is QA work underway on the current release that may turn up new things that need fixing by the end of the week (b) there is a simple workaround in PUP-7216 which is that you can s/hiera_hash/lookup/ as the function that you call. --eric0 On Wednesday, February 15, 2017 at 10:35:32 AM UTC-8, François Lafont wrote: > > On 02/15/2017 05:44 PM, Moses Mendoza wrote: > > > Thanks all for the reports. A fix is in progress / en route, trackable > via > > https://tickets.puppetlabs.com/browse/PUP-7215 > > Ah ok, thanks Moses for the information. > > I have tested in my testing VM and the commit of Thomas Hallgren seems > to work well. :) > > François Lafont > -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f434713b-bb4d-4446-95af-e864d3e57123%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
Hey, it looks like everyone found this, but I wanted to add that we updated this document with the hiera.yaml v5 format late last week, so if you were looking for it outside of the google doc, it's up and running. https://docs.puppet.com/puppet/4.9/lookup_quick.html#there-are-two-hierayaml-formats-now This is an interim update while the docs team work on the full update, which will be out in the next week or two. --eric0 On Tuesday, February 14, 2017 at 9:22:53 AM UTC-8, Bob wrote: > > The spec appears to be here - > > https://docs.puppet.com/puppet/4.9/lookup_quick.html > > On Wednesday, February 8, 2017 at 8:37:32 AM UTC+13, Joshua Schaeffer > wrote: >> >> Okay I see that they are actually preparing to release Puppet 4.9.2 which >> is supposed to fix these issues. Does this mean they will release a new >> puppet-agent package part of the PC1? Where can I go to track the progress >> of this minor release? >> >>> -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5f3712f1-90a2-4f19-8447-9bffdbc77239%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: hiera deep hash merges broken
On 02/15/2017 05:44 PM, Moses Mendoza wrote: > Thanks all for the reports. A fix is in progress / en route, trackable via > https://tickets.puppetlabs.com/browse/PUP-7215 Ah ok, thanks Moses for the information. I have tested in my testing VM and the commit of Thomas Hallgren seems to work well. :) François Lafont -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4e3ff038-da51-62dc-4620-60b398b28816%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] ensure_resource should be the default behaviour
Hi, After some years of writing puppet modules, I think the ensure_resource behaviour (from stdlib) should be the default behaviour for all resources. This will simplify the code, and made Puppet more accessible for beginners. Ref. https://forge.puppet.com/puppetlabs/stdlib/readme#ensure_resource Takes a resource type, title, and a hash of attributes that describe the resource(s). If the resource already exists, but does not match the specified parameters, this function attempts to recreate the resource, leading to a duplicate resource definition error. So I think I'm not the first to ask for this, so why not ? Best regards -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/571039f1-c85f-198b-dcf2-689e38d208f0%40quake.fr. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: hiera deep hash merges broken
On Wed, Feb 15, 2017 at 06:47 Francois Lafont < francois.lafont.1...@gmail.com> wrote: > Oops, I have forgotten to say this: > > On 02/14/2017 08:51 PM, Daniel Urist wrote: > > > Just found this issue, which seems to describe what's going on: > > https://github.com/TomPoulton/hiera-eyaml/issues/222 > > So eyaml is broken wrt hash merges? Are there any workarounds available? > > Currently, the problem happens with puppet-agent version 1.9.x. > No problem with the version 1.8.3. So it could be a temporarily > workaround. Thanks all for the reports. A fix is in progress / en route, trackable via https://tickets.puppetlabs.com/browse/PUP-7215 > > François Lafont > > -- > 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, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/c473132b-b49f-2081-44dd-26fecc216b7f%40gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Moses Mendoza Puppet -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2B421WYfqwb4EcotfiGJidY0TvurApQtQCuRRK%3DPDAzy5DS2gA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: hiera deep hash merges broken
Oops, I have forgotten to say this: On 02/14/2017 08:51 PM, Daniel Urist wrote: > Just found this issue, which seems to describe what's going on: > https://github.com/TomPoulton/hiera-eyaml/issues/222 > So eyaml is broken wrt hash merges? Are there any workarounds available? Currently, the problem happens with puppet-agent version 1.9.x. No problem with the version 1.8.3. So it could be a temporarily workaround. François Lafont -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c473132b-b49f-2081-44dd-26fecc216b7f%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: hiera deep hash merges broken
Hi, On 02/14/2017 08:51 PM, Daniel Urist wrote: > Just found this issue, which seems to describe what's going on: > https://github.com/TomPoulton/hiera-eyaml/issues/222 > So eyaml is broken wrt hash merges? Are there any workarounds available? I have exactly the same problem here, and no solution. And the problem is that "eyaml" seems to be abandoned. So there is a little problem here. I'm very interesting in any information. I think eyaml is widely used. François Lafont -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d0ddf059-2b1d-e2de-0004-1dc24854220d%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Augeas and custom lenses?
On 15/02/17 10:38, otheus uibk wrote: > Hi Dom, > > The puppet documentation you references is just slight on details (well, > that could be said about lots of projects these days). If you're replying to a five year old thread(!), some context would be handy. For reference: https://docs.puppet.com/puppet/latest/plugins_in_modules.html > Does puppet put such lenses in its own directory? Yes, in the agent's libdir, under augeas/lenses/. > Does puppet ensure such lenses override the "default" ones mentioned in the > augtool > page? Yes. The agent directory is specified as an include directory to Augeas, which always has precedence over Augeas' default directories. > All that is mentioned is "Facts and Augeas lenses are used solely > by Puppet agent." But that's not really true of facts, as their > visibility, once installed, are global. Custom facts from Puppet are read only when the additional agent directory is included (i.e. with Facter's -p flag). Lenses work in a very similar way - they are not installed globally. -- Dominic Cleal domi...@cleal.org -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c6104d3d-026e-04d9-c795-1592cc20a58b%40cleal.org. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Augeas and custom lenses?
Hi Dom, The puppet documentation you references is just slight on details (well, that could be said about lots of projects these days). Does puppet put such lenses in its own directory? Does puppet ensure such lenses override the "default" ones mentioned in the augtool page? All that is mentioned is "Facts and Augeas lenses are used solely by Puppet agent." But that's not really true of facts, as their visibility, once installed, are global. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/9d03a137-c8b6-493f-80ad-5d7ebc4af642%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
