terminology on API tokens is no longer valid

[bsutton]

The caddy-dns readme talks about cloudflare api tokens, however the terminology doesn't appear to match the current cloudflare terminology and is ambiguous.

The caddy-dns readme states:

two ways of configuring API tokens.

This statement is ambiguous as there are two types of cloudflare api tokens - user and account.

you will need to change from using a Cloudflare API Key to a scoped API Token

I can find no where in the cloudflare documentation that refers to any token as a 'scoped api token'.

From the cloudflare api documentation:

https://developers.cloudflare.com/fundamentals/api/get-started/create-token/

Determine if you want a user token or an Account API token. Use Account API tokens if you prefer service tokens that are not associated with users and your desired API endpoints are compatible.

I'm guessing that the doco should refer to a User API Token.

[bsutton]

I should note that the caddy page that links to the project also incorrectly mentions scoped api tokens.

https://caddyserver.com/docs/modules/dns.providers.cloudflare

PI token is used for authentication. Make sure to use a scoped API token, NOT a global API key. It will need two permissions: Zone-Zone-Read and Zone-DNS-Edit, unless you are only using GetRecords(), in which case the second can be changed to Read.

[mholt]

Thanks for the heads up. Would you be interested in providing a quick PR? Both can be remedied from this repo.