The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
verbose and debug options always force console log destination
|Affected Puppet version:||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
Some applications, particularly agent, force
options[:verbose] are set. This is regardless of, and in addition to, any user options set via ‘—logdest’. This leads to duplicate messages if the user specified destination also writes to STDOUT. It also makes it impossible for a user to ‘silently’ run some applications without catching STDOUT.
The handling of log destinations seems a bit haphazard in the applications. The apply & inspect applications work as I’d expect, processing —logdest then setting the default with
Puppet::Util::Log.newdestination(:console) unless options[:logset]. Others, like agent queue & application.rb always force
newdestination(:console) when (IMHO) unrelated options like loglevels are set.