Issue #8350 has been updated by Jeff McCune.
# Not too bad #
This isn't too bad to switch everything to the log destination, but we were
printing out a simple "." while waiting on AWS and such. We now get pages and
pages of the following:
<pre>
info: Still waiting for SSH host key fingerprint from AWS ...
[0/1963]
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Still waiting for SSH host key fingerprint from AWS ...
info: Waiting for SSH host key fingerprint from AWS ... Done
</pre>
I'm not sure what to do about this.
# Must run verbose #
With this change, the default behavior of Puppet.info() is to NOT send anything
to the console. To get any feeback the end user must supply the --verbose flag.
I'm not happy with yet another option that doesn't have a sane default, but I
don't really mind making the change anyway.
Thoughts?
----------------------------------------
Refactor #8350: All output should go to a log destination
https://projects.puppetlabs.com/issues/8350
Author: Jeff McCune
Status: Accepted
Priority: Normal
Assignee: Jeff McCune
Category:
Target version:
Keywords: cloudpack, faces
Branch:
# Overview #
We're currently using print and puts in Cloud Pack and this breaks the ability
to pipe rich data into other actions.
In addition, informational messages do not adhere to the standard log
destination configured by the end user.
--
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.
