[Puppet Users] Blacklisting facts by key/value name

2023-02-24 Thread Boris Behrens
"en", "eth", ... and "lo". I tried to wrap my head around the documentation but for me it looks like I can only blacklist entire sections. Cheers Boris -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To

[Puppet Users] Is there an API for retrieving node state?

2015-05-25 Thread Boris Modylevsky
I would like to retrieve a status of a node to know what is its state. I read this documentation, but could not find it: http://docs.puppetlabs.com/puppet/4.1/reference/http_api/http_catalog.html Thanks, Boris -- You received this message because you are subscribed to the Google Groups

[Puppet Users] Re: Puppet resource scoping issue

2013-01-17 Thread Boris
Thanks a lot for the explanation! It became much clearer to me. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/YuB-DKkwiJoJ. To post to this group, send e

[Puppet Users] Puppet resource scoping issue

2013-01-16 Thread Boris
I have a service resource in class 'foo', and i want to make a relationship with this resource from class 'bar'. Both 'foo' and 'bar' classes are included in my node definition. >From puppet docs i learned that dynamic scoping is still available for resources, but what happens in reality, is fro

[Puppet Users] Re: Changing Agent Environment Via Custom Fact

2012-12-20 Thread Boris
Why not make puppet.conf.erb and pass it your env-vatiable. But you will need to run puppet agent once more to apply catalog from new env. четверг, 20 декабря 2012 г., 5:16:27 UTC+4 пользователь joel johnston написал: > > It is very likely that I don't completely understand the order of > opera

[Puppet Users] Puppet 3.0.1: time spent fot "File" resource increased

2012-12-20 Thread Boris
After updating master from 2.7.12 to 3.0.1 I noticed, that agents began spending more time on "File" resources, which I can see from --summarize output: about 40-45 seconds now, and about 25-30 before update. What could cause this problem? I also noticed, that "preferred_serialization_format