Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

info --shell output doesnt match docs #108

Open
tescalada opened this issue Jun 3, 2016 · 0 comments
Open

info --shell output doesnt match docs #108

tescalada opened this issue Jun 3, 2016 · 0 comments

Comments

@tescalada
Copy link

heroku info myapp --shell doesnt produce the same results as the help documentation.

The help docs are correct and would be usable in a bash shell. The actual results are not easily usable for some fields.

Any fields that should have an _ are being replaced by a - because of the S(k).slugify().

const S = require('string')
S('git_url').slugify()
{ [String: 'git-url'] s: 'git-url', orig: 'git-url', length: [Getter] }

Example below (with personal info removed).

$ heroku help info myapp --shell
Usage: heroku info

show detailed app information

-a, --app APP # app to run command against
-j, --json
-r, --remote REMOTE # git remote of app to run command against
-s, --shell # output more shell friendly key/value pairs

Examples:

$ heroku apps:info
=== example
Git URL: https://git.heroku.com/example.git
Repo Size: 5M
...

$ heroku apps:info --shell
git_url=https://git.heroku.com/example.git
repo_size=5000000
...

$ heroku info myapp --shell
create-status=undefined
git-url=https://git.heroku.com/myapp.git
web-url=https://myapp.herokuapp.com/
repo-size=13 MB
slug-size=57 MB
region=us
dynos={}
stack=cedar

tescalada added a commit to tescalada/heroku-apps that referenced this issue Jun 3, 2016
fixes heroku#108
Update the info --shell output to use the keys as passed instead
of using slugify to convert them. This will make it match the docs
and be usable in a bash shell.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant