The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Cloud Provisioner should output info to stderr and data to stdout
|Assignee:||Pieter van de Bruggen||% Done:|
|Target version:||Commercial edition - PE 3.x|
|Keywords:||cloud provisioner node node_vmware list parseable parse binary annoying||Affected URL:|
|Branch:||Affected PE version:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This ticket may be automatically exported to the ENTERPRISE project on JIRA using the button below:
It annoys the crap out of me (And I’m the one who added these message) that when I run this command less thinks I have a binary file because of the color codes.
I expect STDOUT to only contain data I can actually work with using standard unix tools like grep, sed, less, awk, etc…. Things that are for my information as a human should go to stderr.
% puppet node_vmware list > foo.txt ; less foo.txt Locating: 100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:02 "foo.txt" may be a binary file. See it anyway?
#3 Updated by Jeff McCune about 2 years ago
Nigel Kersten wrote:
Does this required changes to Faces or underlying Puppet Jeff? Or is this purely a problem with this Face?
I don’t think it requires changes to the faces framework, but I think the underlying Faces framework should directly support this need.
If it doesn’t, then each face will be responsible for adopting this convention as a best practice. We can make this nice and easy for developers using the framework.
Sort of like how we saw the ProgressBar class move from Cloud Provisioner VMWare up into Cloud Provisioner. I think this follows that pattern, get the good functionality as close to the framework as possible.