CLI enable environment selection about vonage-node-sdk

[cbetta]

I had not even noticed this issue wasn't on the CLI project. Let's close this one and re-open on the CLI library.

[cbetta]

@ramzeaslan great idea. Would the host url be a full url, or just a domain, or also a port? Would this url be predictable? If so can we just do nexmo balance --host dev?

[leggetter]

@cbetta I think it'll be a host, probably including scheme e.g. http://internal-api.nexmo.com

[ramzeaslan]

@leggetter and @cbetta , I reckon having the full host makes the most sense, otherwise we are restricting ourselves and as such are less future proof.

Another alternative which is worth considering is that as part of the setup of the Nexmo CLI you are required to set your API key and Secret, what if you also set your env as part of the setup?

Thanks

[cbetta]

@ramzeaslan interesting. Does make things easier to use. Let me think about it.

[leggetter]

It feels like we're moving more towards a per-project config rather than global config that you'll have to change as you move between environments.

IMO Nexmo/nexmo-cli#109 could be a related to this. How nexmo-node enables it is a good question. But this discussion is really related to the CLI rather than nexmo-node.

To enable this we just need to make the host configurable within nexmo-node.

[cbetta]

Closing, have opened Nexmo/nexmo-cli#114 instead.