[feature] CLI add command (add-api, add-consumer)

[thibaultcha]

Part of improvements needed for the CLI described in #92. Sugar method of adding APIs and Consumers to Kong:

$ kong add-consumer --username jason
[WARN] No configuration at: /etc/kong/kong.yml using default config instead.
[INFO] Using configuration: /usr/local/lib/luarocks/rocks/kong/0.2.0-1/conf/kong.yml
[OK] Consumer added to Kong: username=jason created_at=1429732358000 id=bc7159a9-8c1b-4274-c284-364f64fe4481

$ kong add-api --name mockbin --public-dns mockbin.com --target-url http://mockbin.com
[WARN] No configuration at: /etc/kong/kong.yml using default config instead.
[INFO] Using configuration: /usr/local/lib/luarocks/rocks/kong/0.2.0-1/conf/kong.yml
[OK] API added to Kong: name=mockbin target_url=http://mockbin.com id=fb37eb8a-623c-4916-c923-976f5e523c69 public_dns=mockbin.com created_at=1429732399000

What could be improved:

• Parsing of the arguments. Because of the library we are using, the way they are written in the examples above is the only way to send arguments. No --username='jason' for example.
• Output maybe

[thibaultcha]

@thefosk thoughts? @nijikokun do you see this being simpler for the docs?

[nijikokun]

so this starts an instance and executes, does it also check if an instance is already running?

[thibaultcha]

It does not start any instance, just expects cassandra to be running.

[nijikokun]

Then why the configuration output? I guess it is to tell you which instance its being done to?

[thibaultcha]

Because it's mandatory like any Kong command, it needs the configuration, in this case for the cassandra properties.

[nijikokun]

Hmm, seems a bit verbose, but alright.

Output could be a little bit better, on multiple lines for the data so its easier to read, and spot potential mistakes.

I think it would also require update and remove.

---

Something I was thinking of was kong api --add [type] [arguments] perhaps its too much, was also thinking about kong (add,update,remove) but that could conflict with future commands.

[thibaultcha]

We don't need to deal with the API so let's not bother. kong add [type] [arguments] could be enough. But because of the way the CLI is built, I wanted to have smaller commands, with a smaller purpose. Hence why add-api and add-consumer.

I think update is overkill, remove why not.

[thibaultcha]

It's only verbose because I'm using the utils method to retrieve a configuration, and it outputs logs when it runs, only to inform the user like the other commands. If it's verbose here, it might be in other commands too.

[ahmadnassri]

I'm not sure it's a good idea to use none official sources?

[thibaultcha]

It is official, it is a mirror on the official download page. This change shouldn't be here anyways, oops.

[ahmadnassri]

oh, I just saw the domain and it looks like some guy's personal site ...

[thibaultcha]

What actually happened is that some day, all of a sudden, version 2.1.{3 I think} just disappeared from the main repo, without any notice... I used this mirror which still had it but after a while it disappeared too. Turns out we don't have a choice but to update to 2.1.{4,5}, which we did already in master.

[ahmadnassri]

ah-mazing!

[thibaultcha]

Added a ready label because as discussed with @sinzone, this is ready to be merged anytime as is. more can be added to it later.

[coveralls]

Coverage decreased (-0.02%) to 62.12% when pulling d2ebdc9 on feature/cli-add into 486f374 on master.

[sonicaghi]

@thibaultcha remember to merge this before 0.4

[thibaultcha]

That's not as easily doable as before because the CLI arguments parsing expects one letter args names (-n for --name) but now that an API can have a public_dns and a path, we can't have two -p arguments. And it doesn't accept --path and --public_dns. I would like to find another parsing library/script and implement this for more entities, as well as maybe adding more interactions