Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] - Output format #72

Closed
axos88 opened this issue Jan 20, 2020 · 9 comments · Fixed by #402
Closed

[Feature] - Output format #72

axos88 opened this issue Jan 20, 2020 · 9 comments · Fixed by #402
Assignees
Labels
enhancement New feature or request

Comments

@axos88
Copy link

axos88 commented Jan 20, 2020

Is your feature request related to a problem? Please describe.
Parsing output with scripts

Describe the solution you'd like
An easy way to output say a csv or json document, or something that can be easily parsed programatically

Describe alternatives you've considered
Regexes.......

@axos88 axos88 added the enhancement New feature or request label Jan 20, 2020
@sergerdn
Copy link

Pls also have a look https://github.com/digitalocean/doctl:

Flags:
  -t, --access-token string   API V2 access token
  -u, --api-url string        Override default API endpoint
  -c, --config string         Specify a custom config file (default "$HOME/.config/doctl/config.yaml")
      --context string        Specify a custom authentication context name
  -h, --help                  help for doctl
  -o, --output string         Desired output format [text|json] (default "text")

@yamada95
Copy link

I do want a --no-header flag when listing instance, so I can do batch operation in bash shell easier.

@relwell relwell mentioned this issue Dec 13, 2022
@Justinzobel
Copy link

I'd still love a CSV output as it's a much simpler format to work with in many scripts.

@fharper
Copy link

fharper commented Jun 21, 2023

JSON output format would be great!

@Levilutz
Copy link

Levilutz commented Sep 1, 2023

This change would be great, and would go miles towards more convenient migration to Vultr from competitors. Any movement since @relwell's PR? @optik-aper you mentioned govultr changes that superseded that PR, are those visible anywhere?

@optik-aper
Copy link
Member

@Levilutz Sorry, somehow I missed this mention. The changes are in govultr so yeah, we can make this a priority seeing that there is so much demand. I'll try to get it in for the next minor release.

@optik-aper optik-aper assigned optik-aper and unassigned ddymko Oct 23, 2023
@chrisdeeming
Copy link

Any updates to this @optik-aper? It looks like we were very close to having this via #292 which was closed over a year ago. I'd like to transition to using the CLI but I won't be able to do that until the output can be parsed programmatically via JSON.

Many thanks!

@optik-aper
Copy link
Member

@chrisdeeming It's my main focus at the moment and I'm almost done. The next release will support a --output json flag on all commands.

@chrisdeeming
Copy link

@chrisdeeming It's my main focus at the moment and I'm almost done. The next release will support a --output json flag on all commands.

Nice. Great work! Will be excited to check it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants