Support API Tokens about cloudflare-cli

[danielpigott]

Definitely would be good to support this, though I would want to ensure it is backwards compatible.
I will take a look and update this issue with my suggestions.

[danielpigott]

I have now published the changes as v4.0.0

[danielpigott]

What I am thinking is:

• add 2 new options
  • --api-token (option), apiToken (yml), CF_API_TOKEN (env var)
  • --api-key (option), apiKey (yml), CF_API_KEY (env var)
• deprecate the old --token (option), token (yaml) and remove in the next major release

Keen to hear your thougts.

[aequasi]

There is also the "org id"

[dannyockilson]

What I am thinking is:

• add 2 new options

  • --api-token (option), apiToken (yml), CF_API_TOKEN (env var)
  • --api-key (option), apiKey (yml), CF_API_KEY (env var)

• deprecate the old --token (option), token (yaml) and remove in the next major release

Keen to hear your thougts.

Think that sounds like a clean way of handling it :) They sure got it through beta phase quickly so guess a move to that as the primary auth mechanism would be a good idea.

[dannyockilson]

Sorry been really busy the last few weeks will get back to you with a PR once I get a chance (hopefully in the next few weeks)

[darthwalsh]

I just hit the error message The following required parameters were not provided: email from a fresh npm install which doesn't have the latest master commits, but I did a git checkout and my API token is working great.

It looks like you could publish to npm with what you have now?