Issue #4950 has been updated by Markus Roberts.
Category set to logging
Status changed from Unreviewed to Accepted
Affected version set to 0.25.0
This is because it's hard coded:
<pre>
notice "Tidying %s" % file.ref
</pre>
It appears that several other types do the same thing; of the providerless
types only exec tries to adjust its log destination, with this monstrosity:
<pre>
if log = @resource[:logoutput]
case log
when :true
log = @resource[:loglevel]
when :on_failure
unless self.should.include?(@status.exitstatus.to_s)
log = @resource[:loglevel]
else
log = :false
end
end
unless log == :false
@output.split(/\n/).each { |line|
self.send(log, line)
}
end
end
</pre>
----------------------------------------
Bug #4950: tidy resource ignores loglevel parameter
http://projects.puppetlabs.com/issues/4950
Author: Bruce Richardson
Status: Accepted
Priority: Normal
Assignee:
Category: logging
Target version:
Affected version: 0.25.0
Keywords:
Branch:
No matter what the loglevel parameter is set to, the tidy resource will always
log deletions at 'notice' level.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
