iron-io
Update CLI to support entire developer workflow (entire API?)
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.
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?
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/
Two more things that comes to mind:
-
heroku/gcloud loginwhich 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.
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.
Great cli experience - Greg