Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Provide un-decorated output of all commands for easier parsing #488

rwdaigle opened this Issue Jul 30, 2012 · 4 comments


None yet
2 participants

rwdaigle commented Jul 30, 2012

Re: https://github.com/heroku/devcenter-content-tickets/issues/608

The new heroku addons output format makes it difficult to pipe to other commands because of the existence of the === app Configured Add-ons style headers. Consider the following command to store an app's list of add-ons (which could then be consumed by another command to recreate them on another app).

heroku addons --app bamboo-app > addons.txt

Instead of just reading this file in line-by-line the user would have to manually remove/skip the first line before reading the rest of the file.

Can we think about this use-case more, perhaps think about a -c (concise) standard flag for all commands? It feels wrong that our CLI commands are so brittle to output formatting changes.


geemus commented Jul 30, 2012

@rwdaigle - I'd like to add a global option for this in some way/shape/form. I'm afraid it is tricky for addons in particular though as there can be a separate non-configured header/list. Without the headers, how would one differentiate between the two listings? Outside of the migration context is this a common use case? Could we simplify migration via a plugin with helper commands to avoid the more manual parts of this?


rwdaigle commented Jul 30, 2012

A plugin would help this particular use case, but I believe we've talked about "pipability" for some other commands in the past so this has been a recurring theme (for me, at least). I am in favor for a more universal way to ensure output consistency.


geemus commented Jul 30, 2012

@rwdaigle - noted. If you have other particular use cases where this comes up it would be quite helpful for me if you could explain. I'm not entirely confident that plugins or other things are the best way, but I have a sneaking suspicion that pipability comes from missing capabilities (at least in many cases) and that end-users should have easier ways to do it instead of being bash-awesome. I for instance am fairly bash-awful.


geemus commented Aug 13, 2012

@rwdaigle - I think after our discussion I at least partially convinced you that doing this globally may not be feasible (at least in the short term) due to the sheer volume of information the tool provides now (and how much we would need to pare some default outputs down to facilitate). So I'm going to close this general-case bug, but please open bugs around any particular commands that either really need this style for usage or seem like they are just short of giving you what you need so that we can deal with them. Maybe over time we can pare down the other stuff (and I certainly keep this in mind for new commands), but for now a global version of this seems less than actionable.

@geemus geemus closed this Aug 13, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment