The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #10659

Cloud Provisioner should output info to stderr and data to stdout

Added by Jeff McCune over 2 years ago. Updated 7 months ago.

Status:AcceptedStart date:11/08/2011
Priority:NormalDue date:
Assignee:Pieter van de Bruggen% Done:

0%

Category:cloud provisioner
Target version:Commercial edition - PE 3.x
Keywords:cloud provisioner node node_vmware list parseable parse binary annoying Affected URL:
Branch: Affected PE version:

We've Moved!

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:


Description

Overview

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?

Related issues

Related to Puppet Enterprise (Public) - Bug #12360: Status output should go to stderr Closed 02/01/2012

History

#1 Updated by Jeff McCune over 2 years ago

  • Description updated (diff)

#2 Updated by Nigel Kersten over 2 years ago

Does this required changes to Faces or underlying Puppet Jeff? Or is this purely a problem with this Face?

#3 Updated by Jeff McCune over 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.

#4 Updated by Nigel Kersten over 2 years ago

If this is a suitable change to go into 2.7.x, by all means commit it higher.

I’m happy to let you target which PE version this is suitable for, given our desire to be better about breaking interfaces in point releases.

#5 Updated by Michael Stahnke over 2 years ago

  • Status changed from Unreviewed to Accepted

#6 Updated by Jeff McCune over 2 years ago

2.0.1

Does not need to be in 2.0.1. I’d taget this at 2.5.

#7 Updated by Jeff McCune over 2 years ago

  • Status changed from Accepted to Needs Decision
  • Assignee deleted (Jeff McCune)
  • Target version changed from PE 2.0.1 to PE 2.x

Setting to Needs Decision

I think we need Product / UX / User feedback on these for prioritization and resourcing.

#8 Updated by Anonymous over 2 years ago

  • Assignee set to Pieter van de Bruggen

Pieter, this is close to what you’re investigating now, is it not?

#9 Updated by Pieter van de Bruggen over 2 years ago

This is very close to what I’m thinking about. I should have further thoughts next week.

#10 Updated by Moses Mendoza almost 2 years ago

Pieter, can you update?

#11 Updated by Michael Stahnke about 1 year ago

  • Target version changed from PE 2.x to 409

#12 Updated by Kenn Hussey about 1 year ago

  • Status changed from Needs Decision to Accepted

#13 Updated by Kenn Hussey about 1 year ago

  • Target version changed from 409 to PE 3.x

#14 Updated by Kenn Hussey 7 months ago

  • Category changed from modules to cloud provisioner

Also available in: Atom PDF