https://www.puppet.com/docs/puppet/7/man/agent.html#options
--detailed-exitcodes looks like it might help?
On Mon, 3 Apr 2023, 10:48 Chris Ritson,
wrote:
> Does a manual puppet agent run (puppet agent --test) have a defined exit
> status to indicate if errors were detected? This is not
ort. For this release we are focused
on learning about incompatibilities in module testing.
Please download the new Facter 3 gem and try it out! We would love your
feedback
--
Sean P. McDonald
Software Engineer, Puppet Inc.
--
You received this message because you are subscribed to the Google Gro
://docs.puppetlabs.com/puppet/latest/reference/index.html
--
Sean P. McDonald
Associate Release Engineer, 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 pu
Right. But with a caveat: the random number is not really random. In
fact the random generator is seeded with the node fqdn. Since this is a
constant, the generated random number won't change from run to run for a
given node.
Or if you want to manage cron resource directly:
cron {
On 24 November 2014 at 22:54, Felix Frank felix.fr...@alumni.tu-berlin.de
wrote:
Apparently you should refer to an ActiveMQ module to take care of that
now. I imagine that things will not be much more complicated if you pick
a good module.
https://forge.puppetlabs.com/puppetlabs/activemq
All, I'm encountering teething problems with the MCollective Puppet module,
just in a simple demo/learning mode. Any pointers would be greatly
appreciated.
I'm running puppet-3.7.1-1.el6.noarch from the Puppet repo, both the Puppet
and Dependencies Yum repos are enabled.
puppetlabs/mcollective -
