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

Update CLI to support entire developer workflow (entire API?) #80

Open
treeder opened this issue Aug 18, 2016 · 5 comments
Open

Update CLI to support entire developer workflow (entire API?) #80

treeder opened this issue Aug 18, 2016 · 5 comments

Comments

@treeder
Copy link
Contributor

treeder commented Aug 18, 2016

There should be no need to use HUD, user should be able to use the cli to interact without going to HUD. This may mean to support the entire API in an intuitive way.

@Nyarum Nyarum self-assigned this Aug 18, 2016
@mbbroberg
Copy link

Awesome @treeder - I'd really love to see this fleshed out.

Step 1 of missing functionality is the ability to list out my workers in order to use the CLI further. I can't do anything useful without this part. Sticking with the same syntax that exists now, I'd expect an iron worker list command to be available.

Example:

$ iron worker
worker commands:
        queue
        schedule
        status
        log
        upload
$ iron worker status
error: status takes one argument, a task_id
$ iron worker list
command not found: list
$ iron worker schedule
error: schedule takes one argument, a code name
$ iron worker log
error: log takes one argument, a task_id

Hey @nanliu, we had a good conversation about this after comparing to Heroku and GCE commands. Anything in particular missing for you?

@mbbroberg
Copy link

It may also be helpful to refer to Heroku as an example of a robust CLI you can aim for parity with: https://devcenter.heroku.com/articles/using-the-cli

Those it's a little counterintuitive as a syntax. I prefer Docker's structure (and use of environmental variables): https://docs.docker.com/engine/reference/commandline/cli/

@nanliu
Copy link

nanliu commented Aug 22, 2016

Two more things that comes to mind:

  • heroku/gcloud login which is just a convenience for generating the credential file.
  • easy way access to running instance (not sure if there's an equivalence in Iron.io). Something along the lines of heroku access, gcloud compute ssh.

@treeder
Copy link
Contributor Author

treeder commented Aug 22, 2016

Thanks guys! Very helpful feedback. @Nyarum can you add one for the login? I like that. Perhaps user can set the login credentials for each directory they are in, similar to heroku since each directory would most likely be a different project.

@nanliu we don't have access to instances, the system doesn't really work that way.

@treeder
Copy link
Contributor Author

treeder commented Sep 12, 2016

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

No branches or pull requests

4 participants