• inspect <items...>
• rm <servers...>
• stop <servers...>
• rmi <images...>
• start <servers...>
• restart <servers...>

• start
• exec

• on scw rm, remove server entry
• on scw rmi, remove image||bootscript||volume||snapshot entry
• on GET /resource without filter, replace resource-type cache
• on scw rename, update entry

This is the first step of the Go implementation of scaleway-cli, it consists of creating a skeleton on top of which we can add commands. Since scaleway-cli is highly inspired from the docker-cli which is written in go, we can probably get some inspiration from Docker's repository.

• add facilities to setup the CLI scw login --token=XXXXX --organization=YYYYY
• add a usage message similar to the current CLI
• add basic interaction with the API
• add basic actions (ps)
• add a shared cache for uuids (should handle concurrency)

To reproduce: Try to exec something when the server is starting

➜  ~  scw create Ubuntu_Utopic_14_10
29ba8d8f-5b6c-49a8-8100-cef936aa336b
➜  ~  scw start 29ba8d8f-5b6c-49a8-8100-cef936aa336b
29ba8d8f-5b6c-49a8-8100-cef936aa336b
➜  ~  scw exec 29ba8d8f-5b6c-49a8-8100-cef936aa336b
usage: scw exec [OPTIONS] SERVER COMMAND [ARGS...]. See 'scw exec --help'.
➜  ~  scw exec 29ba8d8f-5b6c-49a8-8100-cef936aa336b ls
➜  ~  scw exec 29ba8d8f-5b6c-49a8-8100-cef936aa336b ls -l
➜  ~  scw exec 29ba8d8f-5b6c-49a8-8100-cef936aa336b ls -la
➜  ~  scw exec 29ba8d8f-5b6c-49a8-8100-cef936aa336b bash
root@determined-thompson:~#
root@determined-thompson:~#
root@determined-thompson:~# exit
➜  ~  scw exec 29ba8d8f-5b6c-49a8-8100-cef936aa336b ls -la
total 28
drwx------  4 root root 4096 Jun  5 14:52 .
drwxr-xr-x 21 root root 4096 Mar 17 15:18 ..
-rw-r--r--  1 root root 3106 Feb 20  2014 .bashrc
drwx------  2 root root 4096 Jun  5 14:52 .cache
-rw-r--r--  1 root root  140 Feb 20  2014 .profile
-rw-rw-r--  1 root root 1240 Mar 17 14:45 .s3cfg.sample
drwx------  2 root root 4096 Jun  5 14:51 .ssh
➜  ~  scw exec 29ba8d8f-5b6c-49a8-8100-cef936aa336b ls -la
total 28
drwx------  4 root root 4096 Jun  5 14:52 .
drwxr-xr-x 21 root root 4096 Mar 17 15:18 ..
-rw-r--r--  1 root root 3106 Feb 20  2014 .bashrc
drwx------  2 root root 4096 Jun  5 14:52 .cache
-rw-r--r--  1 root root  140 Feb 20  2014 .profile
-rw-rw-r--  1 root root 1240 Mar 17 14:45 .s3cfg.sample
drwx------  2 root root 4096 Jun  5 14:51 .ssh
➜  ~  scw exec 29ba8d8f-5b6c-49a8-8100-cef936aa336b bash
root@determined-thompson:~#

• attach
• build
• commit
• cp
• create
• events
• exec
• export
• history
• images
• import
• info
• inspect
• kill
• load
• login
• logout
• logs
• port
• pause
• ps
• pull
• push
• rename
• restart
• rm
• rmi
• run
• save
• search
• start
• stats
• stop
• tag
• top
• unpause
• version
• wait

It'd be cool to have some common examples (like those in the README) accessible from command line, with scw --show-examples for instance.

• inspect
• start
• restart
• stop
• wait
• rm
• rmi

Try to mimics nodejs behavior (#40)

• build
• cp server:path
• export
• import
• load
• logs
• port
• pause
• pull
• push
• rename
• run
• save
• search
• top
• unpause

The following command:

• scw start --sync

Can hang forever if there's a boot issue ; in some scenarii, it is nice to have the ability to set timeouts:

• one for the API state of the server to become OK
• one for the SSH port to be open

These timeouts could be disabled by default, and enabled via CLI options or environment variables or via the config file.

It seems that the // support is not fully complete, sometimes when spawning multiple scw create ..., I get the following stacktraces:

/usr/local/lib/node_modules/scaleway-cli/node_modules/nedb/lib/datastore.js:67
    if (err) { throw err; }
                     ^
Error: ENOENT, rename '/tmp/scw.db~'
    at Error (native)
/usr/local/lib/node_modules/scaleway-cli/node_modules/nedb/lib/datastore.js:67
    if (err) { throw err; }
                     ^
Error: ENOENT, unlink '/tmp/scw.db~'
    at Error (native)

• PostServer
• PostImage
• PostSnapshot
• PostVolume

Maybe we can generate a version.go file from the Makefile with commit ID and version from a somewhere

Then we need to put the information in scw -v and scw version

Currently:

scw exec $uuid 'ls -l'

Prompts to add the SSH key to known hosts (we need to add -k to bypass this check).

Since the usage of this command is primarily for scripting, it would be cool to have -k as the default behavior, and introduce a --safe (or equivalent) extra argument to force the check.