Re: [Puppet Users] Hiera and precedence

2019-01-18 Thread Henrik Lindberg
On 2019-01-17 18:40, Peter Berghold wrote: I'm having a revertment to my noob days with respect to how hiera works.  (Version 3 for now) If I have the hierarchy of - common - nodes/"%{fqdn}" - datacenter/"%{fdatacenter}" if in common.yaml I have "module::parms::server: server1" and in nodes/

[Puppet Users] Use resource only if a tag is given at the command line

2019-01-18 Thread Karsten Heymann
Hi puppet users, is there an easy way to enable a resource only if a certain tag is given? Something like "refreshOnly", but for tags? I'm aware of --skip_tags, but that would require us to specify that on every normal run where the resource is not wanted. Best regards Karsten -- You receiv

[Puppet Users] grep puppet/cache/reports for failures

2019-01-18 Thread Peter K
Can anyone recommend a quick and dirty way to grep through puppet/cache/reports (or whatever $reportdir reports to) to find failures or missing reports? I'm looking for a temporary solution before I commit to setting up reporting software. thx, -peter -- You received this message because you a

[Puppet Users] Puppet-like logging for apply blocks in Bolt

2019-01-18 Thread vlastimil . holer
Hello, I'm not sure if it's possible (I haven't seen it) to provide Puppet-like logging of changed / error resources in *apply* blocks without any additional code. Puppet Agent gives great visibility with default logging level about what has changed and what has failed. Unfortunately, the Bolt

Re: [Puppet Users] Puppet-like logging for apply blocks in Bolt

2019-01-18 Thread Alex Dreyer
Thanks, I agree this output should be available when you're debugging apply statements in plans and I did a spike on implementing this type of logging a few months ago. After some testing it became apparent that this is too much output for the default log level. When running on many nodes it overwh